Even when emmet isn't actually going to do anything with the command, such as when editing a javascript file, the keystrokes still override atoms native keystrokes. Could you address this so that when you aren't focused on a file whose syntax emmet doesn't handle by default, the keystrokes don't get eaten by emmet but rather fall through to the next eligible action.
patrys
commented
9 years ago
Even when emmet isn't actually going to do anything with the command, such as when editing a javascript file, the keystrokes still override atoms native keystrokes. Could you address this so that when you aren't focused on a file whose syntax emmet doesn't handle by default, the keystrokes don't get eaten by emmet but rather fall through to the next eligible action.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.