|Subject:||bug#22295: viper-mode undo bug introduced between Nov 10 and Nov 14|
|Date:||Mon, 16 May 2016 13:06:25 -0400|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2|
On 05/16/2016 08:37 AM, Phillip Lord wrote:
Michael Albinus <address@hidden> writes:address@hidden (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
If you point me to the piece of code where this is done I'll try to recollect why this is done.
My first thought is that it might have something to do with VI-style keyboard macros.
|[Prev in Thread]||Current Thread||[Next in Thread]|