From: uzibalqa <uzibalqa@proton.me>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: From global-set-key to keymap-global-set
Date: Wed, 05 Jul 2023 13:20:11 +0000 [thread overview]
Message-ID: <ez6RPnswofpL7u8r_cAuvHDi5w0at9A1Q1xUImEskiBDdDbCF9g0pqJS1kLeguZJiKr1eOBRl6ohCpAZBTZsLM9m4nsnN-zq-GQw7fQplBM=@proton.me> (raw)
In-Reply-To: <SJ0PR10MB54884384B469448F4AD73C1DF32FA@SJ0PR10MB5488.namprd10.prod.outlook.com>
------- Original Message -------
On Thursday, July 6th, 2023 at 12:56 AM, Drew Adams <drew.adams@oracle.com> wrote:
> > are "keymap-set" and "keymap-global-set" supposed to accept the
> > declarations
> > where command is actually a keymap like so
> >
> > (keymap-set "C-;" "C-x C-;")
> > (keymap-global-set "C-;" "C-x C-;")
> >
> > Which is intended to add the keymap "C-;" as an equivalence to "C-x C-
> > ;",'and
> > thusly having "C-;" as an alternative keymap to using "C-x C-;".
>
>
> What you're calling a "keymap" here is a
> description of a key sequence. It's what
> is acceptable as an argument to `kbd'.
You are quite right on the correct terminology.
next prev parent reply other threads:[~2023-07-05 13:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 16:35 From global-set-key to keymap-global-set uzibalqa
2023-07-04 16:44 ` Eli Zaretskii
2023-07-04 17:11 ` uzibalqa
2023-07-04 17:31 ` uzibalqa
2023-07-04 19:40 ` uzibalqa
2023-07-04 20:26 ` [External] : " Drew Adams
2023-07-04 20:39 ` uzibalqa
2023-07-05 9:44 ` uzibalqa
2023-07-05 11:34 ` Eli Zaretskii
2023-07-05 12:02 ` uzibalqa
2023-07-05 12:46 ` uzibalqa
2023-07-05 12:56 ` Drew Adams
2023-07-05 13:20 ` uzibalqa [this message]
2023-07-05 13:30 ` Eli Zaretskii
2023-07-05 14:01 ` uzibalqa
2023-07-06 8:45 ` Eli Zaretskii
2023-07-06 12:07 ` uzibalqa
2023-07-06 13:53 ` Eli Zaretskii
2023-07-06 14:24 ` uzibalqa
2023-07-06 14:49 ` Eli Zaretskii
2023-07-06 16:01 ` uzibalqa
2023-07-04 18:41 ` Emanuel Berg
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='ez6RPnswofpL7u8r_cAuvHDi5w0at9A1Q1xUImEskiBDdDbCF9g0pqJS1kLeguZJiKr1eOBRl6ohCpAZBTZsLM9m4nsnN-zq-GQw7fQplBM=@proton.me' \
--to=uzibalqa@proton.me \
--cc=drew.adams@oracle.com \
--cc=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).