jps wrote:Just to confirm, this is causing you issues for multi-line sentences, as your workflow is to, say, start at the beginning of the sentence, then shift+down to go down to the next line, then press ctrl+shift+right a few times to get to the end of the sentence?
Hi, Jon. Yeah, It's a problem when I'm writing prose, with wrapping on. With a paragraph of prose in one logical line (ie one terminating CR) but spread over several visual wrapped lines, selecting a sentence spread over several visible lines is now a problem.
The other thing is that I use selection as a preview for deletion, not just copy and cut. I select out what I want gone, get the selection right, and hit delete. If hitting down extends the selection, it threatens to delete code I didn't want deleted. Possibly especially bad when used with shift+pgdn, to select large chunks of code -- say, selecting a binary blob inside an RTF file.
I am generally in the camp of users who want very little extra help from their editor. I use ST as my 'do exactly what I say' editor. , where I can do -exactly- what I mean to my code. So I'd very much prefer it if ST didn't shift my selection start as I move the end, or insert brackets and quotes, or correct my indentation. I'm laying this out explicitly because I think there may be different camps of users, some who want automatic reformatting and helpful selections and such, and some who really won't like it. Me, I'm in the minimalist camp.