Name Change and Key Binding Issues

In Jan 2017 we changed the name of the plugin from "sublemacspro" to "Emacs Pro Essentials". I admit we didn't know the full implications of that name change nor how to test it ahead of time until it was too late.

After fixing the crashes, we then noticed that some of the key bindings were no longer working. The reason for that has to do with the way Sublime manages key bindings: the precedence depends on name ordering of the plugins. It seems like "last one wins" is the strategy and "s" is pretty high in the alphabet while "E" is pretty low. So the emacs pro bindings are lower precedence than they were before.

This essentially means you need to put the emacs bindings you want, that are being overridden by another plugin, in your personal bindings file. Some plugins, e.g., Emmet, allow you to disable some or all of their default bindings with a setting, and that worked well for me in that case.

One of the ways this manifests itself can be slightly confusing. For example, somebody mailed me that "ctrl+k" only worked after you typed another character after it. The reason for that is that there is some other plugin which uses "ctrl+k" as the first key of a multi-key binding, and only after you fail to type a valid second key of a binding does Sublime then go back and offer it to another lower-priority plugin. So if you see things like that, it's all part of this problem.