While editing .sublime-keymap files, "control" as a modifier key name appears to be being erroneously signaled as an error (highlighted in orange [see below]). I just tested it, and even though no occurrences of the "control" modifier key occurs in any of the .sublime-keymap files on my system, Sublime Text does indeed recognize "control" the same as "ctrl", and responds to it correctly in a keymap. So the documentation about it (as a valid modifier key name) here and here are both correct.
vs
I originally thought this was coming from the LSP-json Package, but I was told that highlighting comes from a syntax file in PackageDev. I copied the /path/to/PackageDev/Package/Sublime Text Keymap/Sublime Text Keymap.sublime-syntax to an override Package folder and added "control" to the "modifiers" list on line 10, and it seems to be corrected, so I will submit a PR.
Kind regards,
Vic
While editing
.sublime-keymapfiles, "control" as a modifier key name appears to be being erroneously signaled as an error (highlighted in orange [see below]). I just tested it, and even though no occurrences of the "control" modifier key occurs in any of the.sublime-keymapfiles on my system, Sublime Text does indeed recognize "control" the same as "ctrl", and responds to it correctly in a keymap. So the documentation about it (as a valid modifier key name) here and here are both correct.vs
I originally thought this was coming from the
LSP-jsonPackage, but I was told that highlighting comes from a syntax file inPackageDev. I copied the/path/to/PackageDev/Package/Sublime Text Keymap/Sublime Text Keymap.sublime-syntaxto an override Package folder and added "control" to the "modifiers" list on line 10, and it seems to be corrected, so I will submit a PR.Kind regards,
Vic