|
From: | Michael Kifer |
Subject: | bug#22295: viper-mode undo bug introduced between Nov 10 and Nov 14 |
Date: | Sat, 14 May 2016 16:50:07 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 05/14/2016 04:39 PM, Phillip Lord
wrote:
Michael Kifer <kifer@cs.stonybrook.edu> writes:On 05/14/2016 09:57 AM, Phillip Lord wrote:Eli Zaretskii <eliz@gnu.org> writes:Date: Sat, 14 May 2016 12:25:13 +0300 From: Eli Zaretskii <eliz@gnu.org> Cc: 22295@debbugs.gnu.org, Jim Meyering <jim@meyering.net>Sorry for slow response -- was travelling. Yep, viper is doing strange things to undo -- it adds a symbol ('viper) to the undo list, then removes it later, amalgamating everything upto 'viper.I don't remember much myself, but the issue is this (and it is documented):It's commented rather documented:-) Well, there is no technical documentation like for most other packages. The code is documented though (more or less :-)
Right, it has to do its own marking. When something gets viper-undone, the latest viper-buffer-undo-list-mark is deleted and is replaced with a nil, so that things can be further viper-undone.
I am not sure what you are referring to here.
Something like that. Viper is not the only open-source thing out there :-) -- --- michael |
[Prev in Thread] | Current Thread | [Next in Thread] |