From: Michael Heerdegen <michael_heerdegen@web.de>
To: <tomas@tuxteam.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Which keymap fired in minibuffer?
Date: Tue, 17 Mar 2020 01:23:10 +0100 [thread overview]
Message-ID: <877dzjaky9.fsf@web.de> (raw)
In-Reply-To: <20200316080639.GA10493@tuxteam.de> (tomas@tuxteam.de's message of "Mon, 16 Mar 2020 09:06:39 +0100")
<tomas@tuxteam.de> writes:
> > > Doesn't C-h k tell you?
> >
> > The functions that implement what C-h k says about which map holds your
> > keybinding are `help--key-binding-keymap' and `help--binding-locus' btw.
>
> ...which C-h k would tell you (yeah, sorry, I know *you* know that, but
> I just couldn't let this chance to recurse pass... :)
Should we ever need to write Emacs from scratch (eh, I meant, from
*scratch*) we will surely start with C-h k.
Michael.
next prev parent reply other threads:[~2020-03-17 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 19:05 Which keymap fired in minibuffer? emacs-list-18
2020-03-16 1:10 ` Michael Heerdegen
2020-03-16 2:41 ` Michael Heerdegen
2020-03-16 8:06 ` tomas
2020-03-17 0:23 ` Michael Heerdegen [this message]
2020-03-17 7:50 ` tomas
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=877dzjaky9.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.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.
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).