From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Calling describe-key within el file
Date: Mon, 05 Oct 2020 22:26:30 +0300 [thread overview]
Message-ID: <83tuv8bhjt.fsf@gnu.org> (raw)
In-Reply-To: <trinity-685ed25f-320e-4f50-80cb-a34f7584fd4d-1601924923981@3c-app-mailcom-bs01> (message from Christopher Dimech on Mon, 5 Oct 2020 21:08:44 +0200)
> From: Christopher Dimech <dimech@gmx.com>
> Date: Mon, 5 Oct 2020 21:08:44 +0200
> Sensitivity: Normal
>
> In Emacs, I can get a description of a keybinding combination
> by using "M-x describe-key".
>
> Is it possible to call something like
>
> (describe-key "M-x <up>")
Try
M-x C-h k <up>
prev parent reply other threads:[~2020-10-05 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 19:08 Calling describe-key within el file Christopher Dimech
2020-10-05 19:13 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-10-05 19:16 ` Christopher Dimech
2020-10-05 19:26 ` Eli Zaretskii [this message]
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=83tuv8bhjt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).