I thought I'd add these myself but then found I can't get the source code so I'll pop a request here in the hope it can be added.
First off, a command to clear the selection would be very welcome. This doesn't seem to make too much sense yet but it does in the broader context of what I propose below. It's the lowest priority of the feature requests I present.
Next up are three related commands (the command names are just an example):
* auto_select_on - this acts like shift is being held down for the various navigation commands (cursor keys, page up/down, home/end, etc)
* auto_select_off - stops the above behaviour
* auto_select_toggle - for completeness (although it's not one I'd personally want!)
This way, I could hit a key which is bound to auto_select_on at the start of my selection and then navigate around to where I want it to end then hit a key bound to auto_select_off. I could also have a single key to toggle the behaviour but that's not how my existing preferred editor works.
In my dream world, the selection would then persist even if I do more navigation-type commands to move around my source code. That way, I can page down a bit to look at stuff before making a decision about whether to cut or copy or whatever the selection. Or, I could hit the key I've bound to the new clear_selection command...
If anyone has ever used Zap or StrongED on RISC OS, they will know exactly what I'm talking about and realise just how powerful this mode of operation can be over the very transient selections seen in other editors. I'd love to see this in ST2 (or ST3) - it already does 95% of what I want, which is about 45% more than any other Linux/Windows editor. Cool.
Sarev of Aona