From: Daniel Mendler <mail@daniel-mendler.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 61184@debbugs.gnu.org, rpluim@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict
Date: Tue, 31 Jan 2023 15:53:01 +0100 [thread overview]
Message-ID: <43a2db50-baf4-1fe3-58aa-f375da329c01@daniel-mendler.de> (raw)
In-Reply-To: <834js63i2n.fsf@gnu.org>
On 1/31/23 15:16, Eli Zaretskii wrote:
>> Date: Tue, 31 Jan 2023 13:49:11 +0100
>> Cc: 61184@debbugs.gnu.org, larsi@gnus.org, rpluim@gmail.com,
>> monnier@iro.umontreal.ca
>> From: Daniel Mendler <mail@daniel-mendler.de>
>>
>> The function became less strict since it also accepts vector arguments
>> now.
>
> Because after the change it calls key-description? Or due to
> something else?
Yes, because of the conversion by key-description.
> If the call to key-description is the problem, we could make it only
> in the interactive case, I think? Would that fix the problem?
Yes, that would work as I already suggested in my original mail.
Daniel
next prev parent reply other threads:[~2023-01-31 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:52 bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict Daniel Mendler
2023-01-30 21:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 21:06 ` Daniel Mendler
2023-01-30 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 22:03 ` Daniel Mendler
2023-01-31 3:42 ` Lars Ingebrigtsen
[not found] ` <87zg9zvzuc.fsf@gmail.com>
[not found] ` <871qnbnhhy.fsf@rub.de>
2023-01-31 10:23 ` Robert Pluim
2023-01-31 10:31 ` Stephen Berman
2023-01-31 10:37 ` Robert Pluim
2023-01-31 10:44 ` Stephen Berman
2023-01-31 16:06 ` Eli Zaretskii
2023-01-31 12:10 ` Eli Zaretskii
2023-01-31 12:49 ` Daniel Mendler
2023-01-31 14:16 ` Eli Zaretskii
2023-01-31 14:53 ` Daniel Mendler [this message]
2023-02-03 9:19 ` Robert Pluim
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=43a2db50-baf4-1fe3-58aa-f375da329c01@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=61184@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).