Vim's vi-compatible undo is not limited to single-level -- it just behaves slightly differently than the default Vim undo. Rather than repeating undo with the 'u' key, the 'u' key reverses the undo/redo direction, and Ctrl-R repeats in the current direction. BSD's nvi behaves similarly, but it uses '.' rather than Ctrl-R to repeat. (I hope that explanation is understandable.)

Since I used vi for years before switching to vim, I became accustomed to using repeated presses of 'u' to review my most recent change (undo/redo/undo/redo). I find multi-level undo EXTREMELY valuable though, and wouldn't want to lose that.

Regarding the cursor position after undo... in vim, the behavior is effectively the same as setting a mark at the beginning of every edit operation, then jumping back to that mark (with backquote) after undo.

Thanks for your prompt reply! I'm impressed with ViEmu -- I'm generally skeptical of vi emulation in non-vi editors, because vi has so many subtleties. After using ViEmu for a couple days and seeing your responsiveness to issues, I'm optimistic that I'll be able to use it to improve my Visual Studio experience.

I'll try to explain vi undo mode more concisely: Vim's vi undo mode swaps the undo/redo behavior of ^R and 'u' whenever the user presses 'u'.

I would really like to find a solution to the "cursor position after undo" issue. When I press 'u', sometimes I cannot see what change the undo operation made because the cursor jumps to an entirely different section of the file. I realize this isn't a problem introduced by ViEmu, but I would really like to see ViEmu emulate the vi behavior in this case.

Thanks for being so responsive!

I'm using VS.NET 2005 and C++... but I'm actually not seeing the post-undo cursor position problem anymore. It was very consistently misbehaving during my first Visual Studio session after installing ViEmu, but since restarting Visual Studio I haven't reproduced the problem. I had never seen it behave in the vi way, so thought that was just unaddressed... but now it seems to be behaving exactly as I expect. If I see the problem again, I'll let you know.

For what it's worth, I also noticed (during that same session) that the cursor would jump to an unexpected position after I terminated the debugger.

Select some code and press Ctrl-K, c to comment it. Make some other changes elsewhere in the file. Undo a few times. When you undo the comment operation, the cursor will not move.