From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 14086@debbugs.gnu.org
Subject: bug#14086: 24.3.50; `substitute-command-keys': inappropriate "(that binding is currently shadowed by another mode)"
Date: Sun, 04 Oct 2020 04:41:51 +0200 [thread overview]
Message-ID: <87k0w690gg.fsf@web.de> (raw)
In-Reply-To: <726d8e32-8682-4d03-a558-c02b31c5e679@default> (Drew Adams's message of "Sat, 3 Oct 2020 19:09:17 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Not sure what you're saying. Why should we show the
> shadowed binding? That's the question I was asking
> there. How it comes to be shown was the subject
> above that in the post. But should it be shown?
> If so, why?
It's debatable, sure. But sometimes it's useful info, don't you think?
If you unbind the shadowing key to nil, the other binding will take
effect, so in that sense it is meaningful to the behavior of the keymap.
Do you think we should not list shadowed bindings (and why)?
Michael.
next prev parent reply other threads:[~2020-10-04 2:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 6:04 bug#14086: 24.3.50; `substitute-command-keys': inappropriate "(that binding is currently shadowed by another mode)" Drew Adams
2014-02-10 4:40 ` Lars Ingebrigtsen
2016-04-28 22:49 ` Lars Ingebrigtsen
2016-04-29 11:49 ` Michael Heerdegen
2016-04-29 12:26 ` Lars Ingebrigtsen
2016-04-29 12:42 ` Eli Zaretskii
[not found] ` <<83h9ekwpqj.fsf@gnu.org>
2016-04-29 16:26 ` Drew Adams
2016-04-29 16:29 ` Lars Ingebrigtsen
2020-08-25 11:15 ` Lars Ingebrigtsen
2020-10-03 22:09 ` Michael Heerdegen
2020-10-04 13:58 ` Lars Ingebrigtsen
2020-10-04 17:40 ` Drew Adams
2020-10-04 18:25 ` Eli Zaretskii
2020-10-04 19:13 ` Drew Adams
2020-10-04 23:45 ` Michael Heerdegen
2020-10-05 16:40 ` Drew Adams
2020-10-05 22:33 ` Michael Heerdegen
2020-10-05 23:37 ` Drew Adams
2020-10-05 4:45 ` Eli Zaretskii
2020-10-03 22:48 ` Drew Adams
2020-10-04 1:44 ` Michael Heerdegen
2020-10-04 2:09 ` Drew Adams
2020-10-04 2:41 ` Michael Heerdegen [this message]
2020-10-04 5:00 ` Drew Adams
2020-10-06 21:20 ` Michael Heerdegen
2020-10-06 22:54 ` Drew Adams
2020-10-07 7:22 ` Eli Zaretskii
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=87k0w690gg.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=14086@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
/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).