From: Lars Ingebrigtsen <larsi@gnus.org>
To: 37485@debbugs.gnu.org
Subject: bug#37485: 27.0.50; C-m in describe-bindings
Date: Sun, 22 Sep 2019 23:53:23 +0200 [thread overview]
Message-ID: <87sgooroa4.fsf@gnus.org> (raw)
It's long annoyed med that `C-m' is described thusly by
describe-bindings:
C-c RET Prefix Command
C-c RET C-c mml-secure-message-encrypt
C-c RET C-e mml-secure-message-sign-encrypt
C-c RET C-n mml-unsecure-message
C-c RET C-p Prefix Command
C-c RET C-s mml-secure-message-sign
C-c RET C Prefix Command
C-c RET P mml-preview
C-c RET S Prefix Command
C-c RET b mml-attach-buffer
C-c RET c Prefix Command
I know that `C-m' and RET is the same key binding, but I also think that
when this key is used as a prefix key, I don't think anybody has ever
wanted that to be RET instead of `C-m'.
Or is there a way to distinguish what we mean, somehow?
In GNU Emacs 27.0.50 (build 17, x86_64-pc-linux-gnu, GTK+ Version 3.24.5)
of 2019-09-21 built on marnie
Repository revision: c61bfe0a3adab1a9fd0dc283cbf8291a78ed6da1
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.11902000
System Description: Debian GNU/Linux 10 (buster)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next reply other threads:[~2019-09-22 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 21:53 Lars Ingebrigtsen [this message]
2019-09-23 2:31 ` bug#37485: 27.0.50; C-m in describe-bindings 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
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=87sgooroa4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37485@debbugs.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 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.