You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newlines seem to be treated like words in commands like those bound to b, w, e. Wouldn't it be preferrable to treat them like whitespace? It seems more intuitive to me, and also more useful.
For example when the cursor is on | in the following example
wo|rd
word
pressing w doesn't select until the start of the next word as expected, but stops at the end of the word. Why? I would logically press e if I wanted to do that...
Another example where it bit me:
f(
x)
I wanted to remove the spaces and newlines to obtain f(x). I thought with the cursor after ( I would just do wd but that only removes the whitespace before x, leaving the newlines untouched.
Treating newlines as whitespace would also improve consistency with commands such as extend_next_word_start and delete_word_forward: in the second example for example extend_new_word_start + d could do the job (but this command also stops at the word end in the first example; it could also make sense to change that).
The text was updated successfully, but these errors were encountered:
Newlines seem to be treated like words in commands like those bound to
b
,w
,e
. Wouldn't it be preferrable to treat them like whitespace? It seems more intuitive to me, and also more useful.For example when the cursor is on
|
in the following examplepressing
w
doesn't select until the start of the next word as expected, but stops at the end of the word. Why? I would logically presse
if I wanted to do that...Another example where it bit me:
I wanted to remove the spaces and newlines to obtain
f(x)
. I thought with the cursor after(
I would just dowd
but that only removes the whitespace beforex
, leaving the newlines untouched.Treating newlines as whitespace would also improve consistency with commands such as
extend_next_word_start
anddelete_word_forward
: in the second example for exampleextend_new_word_start
+d
could do the job (but this command also stops at the word end in the first example; it could also make sense to change that).The text was updated successfully, but these errors were encountered: