From: Drew Adams <drew.adams@oracle.com>
To: Fox Kiester <foxkies@gmail.com>, 29203@debbugs.gnu.org
Subject: bug#29203: 26.0.50; Binding a key to (MAP . CHAR) no longer works
Date: Wed, 8 Nov 2017 06:59:47 -0800 (PST) [thread overview]
Message-ID: <8aca0911-3eba-4c46-8a3c-fd3ec6ef5152@default> (raw)
In-Reply-To: <CAOS0dwDiHwuH+8pksf-AM_EMezm=gpMY_i_quCMAE9L+98+NvA@mail.gmail.com>
This is apparently a regression, introduced in Emacs 24.
The problem does not exist in Emacs 20 through Emacs 23.
next prev parent reply other threads:[~2017-11-08 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 2:54 bug#29203: 26.0.50; Binding a key to (MAP . CHAR) no longer works Fox Kiester
2017-11-08 14:59 ` Drew Adams [this message]
2019-11-11 2:32 ` Stefan Kangas
2019-11-11 3:51 ` Drew Adams
2019-11-11 19:09 ` Stefan Kangas
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=8aca0911-3eba-4c46-8a3c-fd3ec6ef5152@default \
--to=drew.adams@oracle.com \
--cc=29203@debbugs.gnu.org \
--cc=foxkies@gmail.com \
/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).