GNU bug report logs - #22295
viper-mode undo bug introduced between Nov 10 and Nov 14

Previous Next

Full log

Message #34 received at 22295 <at> debbugs.gnu.org (full text, mbox):

From: phillip.lord <at> russet.org.uk (Phillip Lord)
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Michael Kifer <kifer <at> cs.stonybrook.edu>, 22295 <at> debbugs.gnu.org,
 jim <at> meyering.net
Subject: Re: bug#22295: viper-mode undo bug introduced between Nov 10 and Nov
 14
Date: Mon, 16 May 2016 13:37:00 +0100

Michael Albinus <michael.albinus <at> gmx.de> writes:

> phillip.lord <at> russet.org.uk (Phillip Lord) writes:
>
>> You don't by any chance remember why viper mode appears to turns itself
>> off in noninteractive mode? Turns out to be rather painful for testing.
>
> You could embed your test code like this:
>
> (let (noninteractive)
>   (run-your-tests))


Yeah, been doing that. Ugly, though, it's not necessary.

The only reason I can think is for people who do lots of "--batch" jobs
and don't want viper to interfere. But, it shouldn't, really, and my
guess is that most people do "emacs --batch -q -l blah.el" for this use.

Phil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.