From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Round-tripping key definitions
Date: Sat, 13 Nov 2021 09:43:15 -0500 [thread overview]
Message-ID: <jwvk0hc6s40.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875yswtzxh.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Nov 2021 05:58:02 +0100")
> It'd be nice if doing a `describe-keymap' would output the same bindings
> that we put in. I mean, on the same form. If you define a key as
> "C-i", that function will describe the key as "TAB", for instance. (And
> the person making that keymap may have meant C-i with "i" being a
> mnemonic for something.)
FWIW, I think the TAB/C-i, RET/C-m, ESC/C-[, DEL/C-? confusion should be
fixed by really decoupling the two.
Maybe one way to do that is to have a `function-key-map` fallback from `[?\C-i]`
to `[TAB]` (so `?\C-i` and `tab` would be "equal partners" both of
which default to falling back to the new `TAB` key).
You say "for instance" above, but which confusing cases are there other
than the four TAB/C-i, RET/C-m, ESC/C-[, DEL/C-? special cases?
> `describe-keymap' could use the :bindings entry to look up the intended
> syntax (and not output that element).
>
> Yeah! I think that should work? (We'd only add this entry if there's
> any "ambiguous" keys in the map, so the impact wouldn't be noticeable, I
> think.)
>
> Thank you for coming to my TED talk.
Truly inspiring. A have a question: how would you define "ambiguous"?
Stefan
next prev parent reply other threads:[~2021-11-13 14:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 4:58 Round-tripping key definitions Lars Ingebrigtsen
2021-11-13 14:43 ` Stefan Monnier [this message]
2021-11-13 14:50 ` Lars Ingebrigtsen
2021-11-13 15:23 ` Stefan Monnier
2021-11-14 0:33 ` Phil Sainty
2021-11-14 14:27 ` Stefan Monnier
2021-11-14 15:07 ` Andreas Schwab
2021-11-14 17:56 ` Stefan Monnier
2021-11-14 18:03 ` Lars Ingebrigtsen
2021-11-14 18:37 ` Stefan Monnier
2021-11-14 18:51 ` Lars Ingebrigtsen
2021-11-14 22:27 ` Stefan Monnier
2021-11-15 5:48 ` Lars Ingebrigtsen
2021-11-15 7:31 ` Lars Ingebrigtsen
2021-11-15 8:21 ` Lars Ingebrigtsen
2021-11-15 21:10 ` Stefan Monnier
2021-11-16 7:41 ` Lars Ingebrigtsen
2021-11-17 8:01 ` Lars Ingebrigtsen
2021-11-16 4:06 ` Richard Stallman
2021-11-17 20:38 ` Stefan Monnier
2021-11-18 2:25 ` Po Lu
2021-11-18 2:48 ` Stefan Monnier
2021-11-18 2:58 ` Po Lu
2021-11-18 11:16 ` Stefan Kangas
2021-11-18 12:31 ` Po Lu
2021-11-19 4:44 ` Richard Stallman
2021-11-18 9:08 ` Lars Ingebrigtsen
2021-11-14 0:39 ` Lars Ingebrigtsen
2021-11-14 14:09 ` Stefan Monnier
2021-11-15 4:53 ` Richard Stallman
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=jwvk0hc6s40.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).