emmet seems to have multiple keybindings for expanding abbreviations. Try ctrl-e and see if it does what you want. You can also look at the Keybinding Resolver (
Packages -> Keybinding Resolver -> Toggle) when you press a key and it will show you all of the commands found for that key as well as the order of priority.
I just turned on
emmet and tested. When I type
div.menu and press tab, the result is
If you share your keymap as well as the output from the Keybinding Resolver package when you try to use the new keybinding, we can help you troubleshoot this.
Could someone explain to me why emmet and autocomplete works so seamlessly in Sublime Text but has all these issues in Atom? What’s different in Atom?
I don’t yet know why
emmet isn’t behaving for you (especially since it does for me), but this set of questions is relevant generally. Atom is a free and open-source piece of software, while Sublime Text is a product you have to pay for. It’s great that GitHub is putting as much effort as they are into giving us this program to use, but working on Atom is not how the developers pay the bills, so they have to limit their time to the parts most central to the goal of the project. The rest of Atom’s functionality is provided by the community, and a lot of packages are very high-quality, but you’re going to have things like functionality conflicts and weird side-effects that will need troubleshooting.