On issue I always had and still have with ST 2 and ST 3 under Windows 7 and Windows 10 with german keyboard layout - currently with ST 3, v3.2, build 3200 under Windows 10:
When the package “expand selection to quotes” is installed, pressing ctrl+# triggers what happens when I press ctrl+7 (toggle comment) and when I press ctrl+shift+# the command for ctrl+shift+7 is being triggered (toggle comment block).
What should happen when I press ctrl+shift+# is “expand selection to quotes” (shift+# types "'" on a german keyboard layout, and shift+7 types "/").
The default keymap for windows defines
{ "keys": ["ctrl+/"], "command": "toggle_comment", "args": { "block": false } },
{ "keys": ["ctrl+shift+/"], "command": "toggle_comment", "args": { "block": true } },
for “toggle comment” and nothing for “expand selection to quotes”, and in my user keymap I defined
[
{ "keys": ["ctrl+7"], "command": "toggle_comment", "args": { "block": false } },
{ "keys": ["ctrl+shift+7"], "command": "toggle_comment", "args": { "block": true } },
{ "keys": ["ctrl+#"], "command": "expand_selection_to_quotes" },
{ "keys": ["ctrl+shift+#"], "command": "expand_selection_to_quotes" },
]
but pressing ctrl+shift+# always triggers the “toggle comment block” command. I am totally clueless here - any hint on what is wrong there?
It’s always been like this for me on different computers under Windows 7 and Windows 10. Pressing ctrl+shift+7 works as defined - it also triggers the “toggle comment block” command.
For tracking issues down, I reproduced this behaviour with only these two packages installed:
"Expand Selection to Quotes",
"Package Control",
Mapping another key than "#" to the expand function work fine, though.