3 ms·
I have absolutely no idea what people are talking about in this thread. I never noticed any of this, and even went right now to test it on Vim 8.0, and nothing
by krick 6y ago
I have absolutely no idea what people are talking about in this thread. I never noticed any of this, and even went right now to test it on Vim 8.0, and nothing of what you are saying seems to be correct. I have quite a big .vimrc, but I don't think I re-configured any of this. Maybe all of it applies only to vi, not vim?
- umanwizard 6y agoTry with `vim -u NONE` to ignore your .vimrc . If the buffer is “asdf jkl” with your cursor at the beginning of the line, after dw the buffer is “jkl”. With the same starting buffer, after cw, the buffer is “ jkl”, with a space at the beginning (which is the same behavior as ce). This “inconsistent” behavior is probably what you usually want, but it does indeed break the invariant that c<motion> is equivalent to d<motion>i .
- chrismorgan 6y ago> the invariant that c<motion> is equivalent to d<motion>i Nit: that invariant also doesn’t work when the motion takes you to the end of the line because of how the cursor is one character wide in normal mode and zero characters wide in insert mode. On a buffer “asdf jkl” with the cursor on the letter f, c$x gets you “asd|” (| representing the cursor location), whereas d$ix gets you “as|d”.