I think the command you want is select_lines
, but it’s bound to Alt+Shift+Up and Alt+Shift+Down by default:
{ "keys": ["alt+shift+up"], "command": "select_lines", "args": {"forward": false} },
{ "keys": ["alt+shift+down"], "command": "select_lines", "args": {"forward": true} },
The commands bound to Ctrl+Shift+Up and Ctrl+Shift+Down are swap_line_up
and swap_line_down
respectively:
{ "keys": ["ctrl+shift+up"], "command": "swap_line_up" },
{ "keys": ["ctrl+shift+down"], "command": "swap_line_down" },
select_lines
adds an extra caret to the line above or below the current line, while swap_line_up
and swap_line_down
shift the location of the current line or selection up and down in the file.
These bindings are from the Default (Linux).sublime-keymap
file. Something that sometimes trips me up when searching for things in the key map is that if you have the regex
mode turned on, +
is special to a regex and doesn’t match the way you expect, so that may be biting you.
A method to determine what command is bound to what keys is to open the Sublime console with Ctrl+` or View > Show Console
and then enter the command sublime.log_commands(True)
in the console to have it log commands as they execute (Do it again with False
or restart Sublime to turn that off).
However if the problem is that the window manager is eating the key before Sublime sees it (which it sounds like it is) that’s not as useful when you’re trying to find what to remap to a key it’s not already using. 