|Subject:||bug#22295: viper-mode undo bug introduced between Nov 10 and Nov 14|
|Date:||Tue, 17 May 2016 10:05:11 -0400|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2|
On 05/17/2016 04:46 AM, Phillip Lord wrote:
Michael Kifer <address@hidden> writes:You see, when I said this is undocumented, I meant precisely that: the expected effect of 'undo' in VI is not described, so someone who is not a VI user doesn't know what to test and how to program that.In VI, an undo is supposed to undo the effect of the previous VI command. In Emacs terms, each such command usually means several inserts and deletes, which in Emacs would be undone via a series of undos. Such behavior is a non-no to a vi user.Actually, by default inserts and (simple) deletes are amalgamated by Emacs and undone in chunks of 20 rather than one at a time.
Yes, but this is semantically meaningless for vi.
I used to have (may still have) access to Solaris where the One True Vi could still be found :-)
True, vim undo is slightly different. But I am not sure there was a vim back when viper started.
Besides, the '.' came from a precursor of viper, introduced by someone else, so I am not responsible :-)
After all these years using it I prefer the viper behavior.
|[Prev in Thread]||Current Thread||[Next in Thread]|