From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: michael_heerdegen@web.de, 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 21:25:09 +0300 [thread overview]
Message-ID: <83h7r9etmi.fsf@gnu.org> (raw)
In-Reply-To: <10de7711-3a84-4e13-ae38-be2b4c93e0fe@default> (message from Drew Adams on Sun, 4 Oct 2020 10:40:55 -0700 (PDT))
> Date: Sun, 4 Oct 2020 10:40:55 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 14086@debbugs.gnu.org
>
> > > seems you treated this in 64d2e5a7a "Make shadowing warning in
> > > describe_map less confusing". Contended enough to close this report?
> >
> > Yeah I think so; closing.
>
> I don't have a way of seeing the change you made.
> Can you please describe it here or include the
> patch here? Usually a patch is included in the
> bug thread, and it's then directly accessible
> from the thread on debugs.gnu.org. A reference
> like "64d2e5a7a" means nothing to me.
It doesn't have to mean nothing. You can point your browser at
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=64d2e5a7a
and se the changes. Note that everything in that URL is fixed, apart
from the commit ID, which is what Lars mentioned. So that ID is a
unique ID of the changeset, and you can always find it as above.
next prev parent reply other threads:[~2020-10-04 18:25 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 [this message]
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=83h7r9etmi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14086@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).