Comment by 😺 gemalaya

Re: "Off by 1 character"

In: s/vim

@mbays Yes that's what i meant. You make a great point with the "special case". I could be wrong but I think that this behaviour has always been there, all the way back to the first original vi version (that was in 1976 ! omg vi is 47 years old). I wonder if developers of clones like neovim ever considered changing that ..

This never bothered me, i know that if i'm at the end of the line and go back to command mode (and the cursor backs up one char), i'll always use 'a' to add some text.

😺 gemalaya

2023-09-06 · 9 months ago

2 Later Comments ↓

🚀 stack [OP/mod] · 2023-09-06 at 01:58:

I got into a bit of trouble with a script some months ago, off by a character in a loop...

🐉 gyaradong · 2023-09-06 at 08:15:

I tend to use 'i' or 'a' depending on context, so I don't know why I'd need to keep tapping 'k' after escaping? Having said that, I know the problem and it does make macros a bit error prone sometimes. vi is not very consistent with key choices overall. For example, often a capital letter is the dual of the lowercase letter, but sometimes not. Is it worth chasing that consistency? Not sure. There are new languages / editors which aim for a more consistent modal typing experience.

Original Post

🌒 s/vim

Off by 1 character — I hate that vim is always off by a character. Let me clarify. When you exit the insert mode, the cursor backs up to the last character entered. So if you insert some text, then delete to the end of the line, vim will eat your last-inserted character unless you move over one. Annoying, right? Or, say you repeatedly enter insert mode then exit back to command line. That is a no-op, right? Wrong: your cursor will move left one character. That seems kind of idiotic. Does...

💬 stack [mod] · 12 comments · 1 like · 2023-09-04 · 9 months ago