Word left/right as in VS Code #42
Replies: 7 comments 2 replies
-
I use VSCode a lot so I'm totally ok with this. |
Beta Was this translation helpful? Give feedback.
-
Similar discussion was here in the past. I think it has sense.
Jan Fiala
…
Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I think it's a good idea. |
Beta Was this translation helpful? Give feedback.
-
Implemented. Please check. Please note:
|
Beta Was this translation helpful? Give feedback.
-
I'd like to reopen this discussion. I may be mistaken, but it seems like Ctrl-Right in the current SynEdit, goes to the beginning of the next word (or symbol), and VSCode seems to go to the end of the current word or symbol. I have to admit that I like the VSCode version a bit better, especially when using Shift-Right. SynEdit will select the current word and any whitespace, while VSCode seems to stop at the end of the word. It's also possible that I've changed some setting in VSCode that changes the behavior. Any thoughts appreciated as always! |
Beta Was this translation helpful? Give feedback.
-
@pyscripter You're correct! I've done some more research and it seems like most applications (and anything that uses standard Windows edit controls) work the way that SynEdit does. VSCode and any program that used the PlusMemo use the alternate way (I've just been using those ones a lot and noticed the difference.) Apologies... I think we can close this one again since I think the current method is more standard. |
Beta Was this translation helpful? Give feedback.
-
Just for the record, PrevWordPosEx was changed recently to align it with Visual Studio, and Visual Studio code. |
Beta Was this translation helpful? Give feedback.
-
Currently if say you have the following expression, the cursor is at the end and you press Ctrl+Left repetitively the cursor stops are indicated below
After the abc the cursor moves to the previous line.
In VS Code and other editors here is what happens:
Similarly for Ctrl+Right.
In PyScripter I have implemented the VS Code approach. Do you think it is more useful than the current approach? Should we replace the current approach with the VS one? (Please do not say provide an option!)
@MShark67,@vincentparrett,@JaFi-cz Any views on this?
Beta Was this translation helpful? Give feedback.
All reactions