From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37485@debbugs.gnu.org
Subject: bug#37485: 27.0.50; C-m in describe-bindings
Date: Mon, 23 Sep 2019 19:07:44 +0200 [thread overview]
Message-ID: <87ftknym8v.fsf@gnus.org> (raw)
In-Reply-To: <83h853ouqi.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Sep 2019 19:14:29 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> I'm not sure I understand...
>
> I meant that users usually press RET, not C-m.
You've done a poll? :-)
>> Both RET and C-m are keys we press, but the intended (both mnemonic and
>> ergonomic) key stroke here is `C-c C-m c' (etc) and not the awkward `C-c
>> RET c'.
>
> Call me awkward, then.
But do you use RET instead of `C-m' in these keystrokes because that's
what `describe-bindings' say or because you prefer to hit `RET'?
Anyway, I've grepped through the *.texi files, and there are 152 matches
for `C-c C-m ...' and 8 for `C-c RET'. And all of those 8 are for RET
as the final character in the keystroke.
If you expand to "C-. C-m"/"C-. RET" it's 170/20. (All those additional
ones are from mule.texi.)
It seems the mode writers' intentions are pretty clear: They mean for
the users to type C-c C-m ..., but `describe-bindings' tells them to type
C-c RET.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-23 17:07 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 [this message]
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=87ftknym8v.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37485@debbugs.gnu.org \
--cc=eliz@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.