Hi, > When in insert mode, cursor is between two chars. When in command mode, > cursor is on top of a char, to make it possible to perform char > operations. When you press escape, cursor either has to move back one > char or forward one char. It can't stay in the place because it's in the > middle and that makes no sense in command mode.
Thanks for the explanation, I wasn't aware of that. > If you were at the end of > line, obviously cursor would not be able to move ahead one char which > means behaviour would be inconsistent. True, but I don't think that'd be a problem. At the end of the line it could move the cursor back one instead of forwards. Vim's current behavior is actually just as 'inconsistent'. It always moves the cursor back one when returning to normal mode... except when the cursor is at the start of a line, in which case it instead moves it forwards one. Personally I feel that moving the cursor forwards when returning to normal mode would be a more useful default. I think that after the user has finished inserting some text the next thing they will want to do is more likely to be concerning text located *after* what they've just inserted (and thus less likely that they will want to do things concerning the last character they've entered or ones prior to that). But anyway, that is just based on my intuitive feel, not any empirical data :) James. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
