From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37485@debbugs.gnu.org
Subject: bug#37485: 27.0.50; C-m in describe-bindings
Date: Mon, 23 Sep 2019 21:44:38 +0300 [thread overview]
Message-ID: <835zliq2cp.fsf@gnu.org> (raw)
In-Reply-To: <87v9tiyjwo.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 23 Sep 2019 19:58:15 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 37485@debbugs.gnu.org
> Date: Mon, 23 Sep 2019 19:58:15 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Key description and fast typing are two separate issues. Mnemonics is
> > yet another, third, issue (and assigning mnemonic value to 'm' in C-m
> > is generally unusual, IME). I don't think these additional issues
> > should affect how we display C-m/RET _everywhere_ in our docs. E.g.,
> > would you propose to use C-i instead of TAB?
>
> Hm... I think so? (There's 67 `C-. C-i' in the manual.)
And 187 TABs.
> Mind you, I'm only talking about multi-key keystrokes if we were to do
> this by default.
I don't see the difference, and neither does describe-key, AFAIK.
> But what I really had in mind was to find out whether anybody had any
> smart ideas for how to convey to `describe-bindings' how these keys
> should be displayed on a per-keymap basis. I hadn't taken a look at how
> keymaps are defined at all...
>
> But they are really char-table objects wrapped in a list?
>
> Would it be possible to add an option to `make-keymap' that would pass
> along an argument to control what `describe-bindings' should do with the
> keymap? And then stash that in the char-table object?
I think it's a waste of cycles. We have much more important stuff to
spend time on. But that's me.
next prev parent reply other threads:[~2019-09-23 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 21:53 bug#37485: 27.0.50; C-m in describe-bindings Lars Ingebrigtsen
2019-09-23 2:31 ` Eli Zaretskii
2019-09-23 10:38 ` Lars Ingebrigtsen
2019-09-23 12:16 ` Andreas Schwab
2019-09-23 13:45 ` Lars Ingebrigtsen
2019-09-23 16:14 ` Eli Zaretskii
2019-09-23 17:07 ` Lars Ingebrigtsen
2019-09-23 17:23 ` Eli Zaretskii
2019-09-23 17:33 ` Lars Ingebrigtsen
2019-09-23 17:50 ` Eli Zaretskii
2019-09-23 17:58 ` Lars Ingebrigtsen
2019-09-23 18:44 ` Eli Zaretskii [this message]
2019-09-23 17:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835zliq2cp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37485@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.