I read the official documentation for using the keyboard to select text on Mac. I am using Mac OX 10.8.4.
sublimetext.com/docs/2/column_selection.html
It states to use
Ctrl + Shift + Up
Ctrl + Shift + Down
It does not work, these keys are used for Mission Control.
Can you please fix your documentation, and explain to me how to use the keyboard to select text?
Thank you.
The documentation is correct.
Disable or change the Mission Control shortcuts and those keys will be passed through to Sublime Text. Or change Sublime Text’s shortcuts.
I always try to be friendly when asking a question, but I am sensing a little attitude. Perhaps I am wrong. So no the documentation is not correct, unless I remap the short cuts. If it was correct it would have worked as is. So if that is the case they should add that to the documentation. There are other shortcuts they could have used, they wasted cntrl + Q + B when it does the same as the left button.
The ST documentation, in my opinion, is lacking. But I accept that. I think adzenith’s point is that without any global shortcut grabbing it before it reaches ST, it does work properly. As Mission Control is a feature in OS X, perhaps it should be noted. But in general, I don’t know that an update is required simply because of some global action. Also keep in mind that jps most likely chose key combinations that would be intuitive to the user, knowing full well that it is easy to customize on a per user basis.
Personally, I don’t try to rely on the official documentation to much . I use the unofficial docs or simply explore myself. For example, it’s very simple to remap those commands (and really any keyboard shortcut). For your particular case, you will want to create a User keybinding. This file will be created for you by going to “Preferences -> Key Bindings - User” This is a JSON file consisting of a list of objects.
{ "keys": "ctrl+shift+down"], "command": "select_lines", "args": {"forward": true} },
{ "keys": "ctrl+shift+up"], "command": "select_lines", "args": {"forward": false} }
]Of course, change the keys to whatever suits you. You can find the command and arguments in one of two ways. First, you may look at the key binding file (Preferences -> Key Bindings - Default). Then look for the key combination you want to identify. Alternatively, you can enter “sublime.log_commands(True)” in the console. This will also display the commands and arguments. For your particular case, the first option would work better.
skuroda,
Thank you for taking the time. I guess my point is that they picked a short cut for ST on Mac that is already used by Mac OX. It would have impossible for them not to know this. I guess I find it somewhat annoying where I actually purchased sublime. Have a great day.
Sublime out-of-the-box has issues on all OSs, in the sense that you need to configure it, including exploring the large plugin ecosystem, to adapt it to your needs. This true of most (all?) sophisticated cross-platform text editors (e.g., vim).
It’s rather frustrating in the beginning, because the docs are a little thin. That said, (and despite the occasional snarky remark 
), these forums are an excellent place to ask for help.
The time I’ve spent customizing Sublime has been worth it for me; YMMV, but give it a shot.
Sometimes I have to accept things. I use vim as well for server stuff. And ultimately you are correct quodlibet… That said when someone tells me something that is wrong, they are getting called on it. Sublime despite being free to use, is something they want the end user to pay for and I paid for it to support it, so I see a clear diff between it and vim. I used to use Textpad in Windows and sometimes I still miss it, their support was excellent. These days I am a Mac and linux user.