-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a whichwrap option? #768
Comments
From the documentation, it sounds like the |
@kirawi you should read the linked documentation, it's about configuring this behavior, not about specific keys :P |
There's no configuration option and I'm not sure if we want this to be configurable. Currently everything wraps: h/l used to stop at the end of line but after a discussion with @cessen we removed this limitation and had it match kakoune. I personally don't use this wrapping behavior, but what's the rationale for explicitly disabling it? |
I would love to see this behaviour back, it was one of the reason why I went back to vim after using kakoune for ~6 months (But overall I'm really in love with helix and don't plan to quit soon even if this behaviour is never implemented! Thanks for all the great works!) |
I personally think this can be nice to have, if a bit niche, but I don't really think there's much of a reason not to make this configurable. Though it barely affects me, I think if it were configurable, I'd turn wrapping off. |
@irevoire just curious what the benefit would be? |
Just preventing complexity, IMO. We've always had 4 directional keys, and making half of them go diagonally only at certain times is plain confusing. |
Yeah, especially when you have multiple cursors and by hitting |
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
* in case count > 1, move as far in the same line as possible without leaving it * also adjust unit tests
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
Commands added: * `move_same_line_char_left` * `move_same_line_char_right` * `extend_same_line_char_left` * `extend_same_line_char_right` * `append_mode_same_line` These new commands move cursors, while making them stay in the same line. So if a cursor would wrap around into another line, instead it won't move and stay at its current position.
Hello,
I would love to have a whichwrap option like in vim.
Basically, the idea would be that, when I'm at the end of a line and type
right
, I should just stay at the end of my line.The same goes for the start of the line and
left
.Is this something planned?
The text was updated successfully, but these errors were encountered: