Replies: 2 comments
|
It is the default behavior in Word, VS Code and Visual Studio (not sure about other major text editors), so it can't be too surprising to users. But your suggestion deserves some thinking. |
0 replies
|
I'll get used to it either way. I do notice that Word only does it for shift-up/down (which I had never noticed.) My favorite PHP/HTML editor appears to do it but only at the bottom of the file and not at the top. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I think this is definitely one of those "what you're used to seems correct" issues and I'm not used to this behavior (but I also don't see it as a major issue btw.) It is a bit of an issue if you use the eoKeepCaretX feature as just pressing up on the top line or down on the bottom line loses your X position. Would it make any sense to make this behavior reliant on eoKeepCaretX? It seems like it's a good use for that option as I don't think it would have any adverse side effects.
-Mark
All reactions