Sublime Forum

Overriding shortcuts

#1

What’s the “protocol” of overriding keyboard shortcuts? What’s the order of precedence?

If conflicting shortcuts are defined in any combination of default-keybindings, user-keybindings, or addon package keybindings, what’s the order of precedence? Which gets enabled 1st/2nd/3rd?

For reference, there’s a keyboard shortcut I’m trying to use (“jump to previous tag/attribute” CTRL-SHIFT-,) but is being overridden somewhere. Its sibling shortcut (“jump to next tag/attribute” CTRL-SHIFT-.) works fine.

I must have a keybinding shortcut conflict somewhere, and am trying to understand the ordering of precedence (for future reference) and track down where the conflict is defined.

0 Likes
#2

From the unofficial docs (though I think they are also in the official ones somewhere)

[quote]Merging and Order of Precedence
Packages/Default and Packages/User also receive special treatment when merging files (e.g. .sublime-keymap and .sublime-settings files). Before merging can take place, the files have to be arranged in some order. To that end, Sublime Text sorts them alphabetically by name, with the exception of the folders Default and User. Files contained in Default will always go to the front of the list and, those in User, to the end.[/quote]

To track down what package is overriding it, try entering “sublime.log_commands(True)” in the console. In addition, you may want to try using the FindKeyConflicts plugin.

0 Likes