GNU bug report logs -
#22295
viper-mode undo bug introduced between Nov 10 and Nov 14
Previous Next
Reported by: Jim Meyering <jim <at> meyering.net>
Date: Sun, 3 Jan 2016 04:03:01 UTC
Severity: normal
Fixed in version 25.1
Done: phillip.lord <at> russet.org.uk (Phillip Lord)
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: phillip.lord <at> russet.org.uk (Phillip Lord)
> Cc: Jim Meyering <jim <at> meyering.net>, 22295 <at> debbugs.gnu.org, jwiegley <at> gmail.com
> Date: Fri, 20 May 2016 12:46:14 +0100
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > FWIW, I think this should go to emacs-25, since (a) the changes affect
> > only viper-mode, and (b) users of that mode will be most unhappy
> > without these changes.
>
> Not quite true. I've changed simple.el.
I've seen the change, of course. As long as only viper-mode uses that
variable, I see no danger.
> > However, we should add comments to viper-cmd.el that document the
> > special handling of 'undo' by viper-mode, and how that interacts with
> > the core 'undo' functionalities. We should also comment in simple.el
> > that undo-auto-disable-boundaries is used by viper-mode, and document
> > that variable in the ELisp manual. Phillip, can you add these bits to
> > the branch, please?
>
> Oh, yeah, sorry forgot the manual. I updated most of the rest last
> night. I think that the branch is ready, bar squashing.
Thanks.
John, we are waiting for your verdict.
This bug report was last modified 8 years and 346 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.