From: John Cummings <john@rootabega.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51253@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#51253: 28.0.60; Meta keys broken when viper is active
Date: Wed, 20 Oct 2021 08:24:54 +0000 [thread overview]
Message-ID: <5enybkUDBpPl8wYH_YZAVjLUeDAyHzlXeCBuC2AeUnLt5E65YIwLvM6XHTY2XWVvaWvmiizx2lwIakNf26CgqwfK1IltK9pffP85tUhzmLU=@rootabega.net> (raw)
In-Reply-To: <878ryop17z.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> wrote:
> John Cummings john@rootabega.net writes:
>
> > > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18182 was fixed in
> > > > 5d522b430bd5ecfb8f082906cd634883dbb68f3e. This changed viper-ESC-key
> > > > from <escape> to ESC, which resulted in a direct key binding of (27
> > > > . 'viper-intercept-ESC-key) while in the viper vi/insert states.
> > >
> > > Maybe that commit should just be reverted?
> >
> > I've looked into this some more, and I think reverting it is the
> > way that the entirety of the viper ESC-handling stack was designed
> > to function.
>
> I've now reverted it in emacs-28, and I'm reopening bug#18182.
Thanks, it's working again on my end! By the way, it had broken both
terminal and gui Emacs, just in different ways (re: the commit message).
I'll see what more I can do about the keymap logic.
prev parent reply other threads:[~2021-10-20 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 20:44 bug#51253: 28.0.60; Meta keys broken when viper is active John Cummings
2021-10-19 23:13 ` Stefan Kangas
2021-10-19 23:32 ` John Cummings
2021-10-20 8:08 ` Lars Ingebrigtsen
2021-10-20 8:24 ` John Cummings [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='5enybkUDBpPl8wYH_YZAVjLUeDAyHzlXeCBuC2AeUnLt5E65YIwLvM6XHTY2XWVvaWvmiizx2lwIakNf26CgqwfK1IltK9pffP85tUhzmLU=@rootabega.net' \
--to=john@rootabega.net \
--cc=51253@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.