From: Drew Adams <drew.adams@oracle.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: RE: (define-key MAP [remap COMMAND] PREFIX-KEY-MAP)
Date: Fri, 27 Sep 2019 14:25:02 -0700 (PDT) [thread overview]
Message-ID: <deecaf3e-b135-471b-b27f-d288ceed40e7@default> (raw)
In-Reply-To: <50d90eb8-10e2-4151-a1db-2eb66c5f92ff@default>
Forgot to add that the doc string of `define-key'
suggests that it IS supported:
DEF is anything that can be a key's definition:
...
a keymap (to define a prefix key)
That description of DEF is written separately from
the description of [remap COMMAND]. There is no
explicit restriction placed DEF for the [remap
COMMAND] case.
Is there a bug here, in the handling of `remap'?
next prev parent reply other threads:[~2019-09-27 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:20 (define-key MAP [remap COMMAND] PREFIX-KEY-MAP) Drew Adams
2019-09-27 21:25 ` Drew Adams [this message]
2019-09-28 3:59 ` Drew Adams
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=deecaf3e-b135-471b-b27f-d288ceed40e7@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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.
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).