From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 14086@debbugs.gnu.org
Subject: bug#14086: 24.3.50; `substitute-command-keys': inappropriate "(that binding is currently shadowed by another mode)"
Date: Sun, 09 Feb 2014 20:40:05 -0800 [thread overview]
Message-ID: <87lhxjbmxm.fsf@building.gnus.org> (raw)
In-Reply-To: <0FF2F801815441C3B5385CE3202E16A0@us.oracle.com> (Drew Adams's message of "Thu, 28 Mar 2013 23:04:25 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> But near the end of the listing (not at all near that entry), I see this
> other entry for `M-r':
>
> M-r previous-matching-history-element
> (that binding is currently shadowed by another mode)
Yeah, kinda awkward way of putting it. What about just
(binding currently shadowed)
?
> That makes no sense, or is at least misleading. There is no special
> "mode" that I am aware of that is involved here, for one thing. And I
> don't see how the `previous-matching-history-element' binding is
> "shadowed", whether by "another mode" or any other way. `M-r' is simply
> bound to `icicle-roundup' in this keymap - it is not bound to
> `previous-matching-history-element' in this map, AFAIK.
>
> Seems like a bug to me. At the very least it is unhelpful and
> misleading for a user who sees this. (Not to mention the fact that this
> extra info, if you think it serves a purpose, is far from the first
> `M-r' entry, so a user will likely see one or the other but not both
> together (unless the keymap has few keys in it).
I think it sounds useful to list bindings that would normally be on the
map unless something had redefined the key.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-10 4:40 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 [this message]
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
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=87lhxjbmxm.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=14086@debbugs.gnu.org \
--cc=drew.adams@oracle.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).