From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: phillip.lord@russet.org.uk, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: viper-mode undo bug introduced between Nov 10 and Nov 14
Date: Fri, 13 May 2016 10:23:40 +0300 [thread overview]
Message-ID: <8360uia0ar.fsf@gnu.org> (raw)
In-Reply-To: <CA+8g5KGNz2DtEQBVwyWx8qqTOQZUkM=2XSPtCt-n01ZDtwGdCg@mail.gmail.com> (message from Jim Meyering on Thu, 12 May 2016 22:01:48 -0700)
> From: Jim Meyering <jim@meyering.net>
> Date: Thu, 12 May 2016 22:01:48 -0700
> Cc: emacs-devel <emacs-devel@gnu.org>, Phillip Lord <phillip.lord@russet.org.uk>
>
> > 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) works once again.
>
> If it is still necessary tomorrow, I'll create a separate bug report.
Yes, please file a separate bug report.
For the record, that commit on the master branch switched viper to
lexical-binding, so reverting it is probably out of the question. We
need to look for a solution that keeps the lexical-binding.
Thanks.
next prev parent reply other threads:[~2016-05-13 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 20:46 viper-mode undo bug introduced between Nov 10 and Nov 14 Jim Meyering
2016-04-15 7:19 ` Eli Zaretskii
2016-05-11 4:33 ` Jim Meyering
2016-05-11 7:54 ` Eli Zaretskii
2016-05-13 5:01 ` Jim Meyering
2016-05-13 7:23 ` Eli Zaretskii [this message]
2016-05-13 15:11 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8360uia0ar.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
--cc=monnier@iro.umontreal.ca \
--cc=phillip.lord@russet.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).