[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: viper-mode undo bug introduced between Nov 10 and Nov 14

From: Jim Meyering
Subject: Re: viper-mode undo bug introduced between Nov 10 and Nov 14
Date: Fri, 13 May 2016 08:11:38 -0700

On Wed, May 11, 2016 at 12:54 AM, Eli Zaretskii <address@hidden> wrote:
>> From: Jim Meyering <address@hidden>
>> Date: Tue, 10 May 2016 21:33:15 -0700
>> Cc: Phillip Lord <address@hidden>, emacs-devel <address@hidden>
>> However, now there is an additional bug in viper mode:
>> When I run e.g., "!!" to tell it to replace the text of the current
>> line with the output of some shell command, I see the usual "!" prompt
>> asking me for that command in the minibuffer. Let's say I type "cat"
>> then enter. So far so good.
>> However, if I type "!!" again, this time I see "!(default cat) ", and
>> let's say I want to accept that default and hit return. Then emacs
>> attempts to run the command "(default cat)". Oops. Even if I type
>> something, it is only appended, so if I type "cat" again, emacs runs
>> "(default cat) cat".
>> This appears to have been introduced some time on or before May 6th.
> On which branch do you see this new problem?  Does it happen on
> emacs-25, the release branch?
> In any case, please file a separate bug report about that, as it
> doesn't seem to be related to the undo problem (AFAIU).

I traced the new problem to commit
088acab3831b45e0e0749705226b8680076df4b6, aka
emacs-24.5-rc3-fixed-9210-g088acab. When I revert that change and
rebuild from emacs.git's master branch, that particular problem (which
also caused repeated "/"-based searching to mistakenly use the
"(default ...)" prefix) goes away.

If it is still necessary tomorrow, I'll create a separate bug report.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]