From: Thibaut Verron <thibaut.verron@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>, help-gnu-emacs@gnu.org
Subject: Re: don't hard-code keys
Date: Sun, 2 May 2021 19:28:12 +0200 [thread overview]
Message-ID: <CAFsi02TeqDgt=fjdGc3UjQN4CUx7pUKhpjshYCY9-dZX7qoNAA@mail.gmail.com> (raw)
In-Reply-To: <8735v5ry9p.fsf@zoho.eu>
On Sun, 2 May 2021, 16:48 Emanuel Berg via Users list for the GNU Emacs
text editor, <help-gnu-emacs@gnu.org> wrote:
> Tassilo Horn wrote:
>
> >> But the question: how can I avoid hard-coding the C-u key
> >> but instead have the keybinding inserted thru a reference
> >> to the function, i.e. `universal-argument'?
> >
> > You mean, in the `message' call? Have a look at
> >
> > (info "(elisp) Keys in Documentation")
>
> I have it working in docstrings but not in general, for
> example this
>
> ‘\[COMMAND]’
> stands for a key sequence that will invoke COMMAND, or ‘M-x
> COMMAND’ if COMMAND has no key bindings.
>
> sounds like what I want but
>
> (substitute-command-keys "\[universal-argument]")
>
> :(
>
You need to escape the backslash, otherwise \[ just becomes [ in the
string.
next prev parent reply other threads:[~2021-05-02 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 22:35 don't hard-code keys Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-02 7:13 ` Tassilo Horn
2021-05-02 14:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-02 17:28 ` Thibaut Verron [this message]
2021-05-02 17:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-02 17:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
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='CAFsi02TeqDgt=fjdGc3UjQN4CUx7pUKhpjshYCY9-dZX7qoNAA@mail.gmail.com' \
--to=thibaut.verron@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).