From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Doc of keyboard macros
Date: Mon, 24 Sep 2018 18:21:40 +0300 [thread overview]
Message-ID: <835zyuc457.fsf@gnu.org> (raw)
In-Reply-To: <jwvva6v550o.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 24 Sep 2018 10:47:55 -0400)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Mon, 24 Sep 2018 10:47:55 -0400
>
> https://emacs.stackexchange.com/questions/44918 points out that `C-x (`
> and `C-x e` are not very visible in the doc, while F3 and F4 may be
> difficult to reach on Apple's machines (and I just saw that they are
> also difficult to reach on my Debian machine for some reason).
> So I suggest making the "old" keyboard macro bindings a bit more
> prominent in the doc (I also happen to prefer them over F3 and F4,
> because of their mnemonic value).
>
> Any objection to the patch below for emacs-26?
No real objection, but:
. You are breaking the manual's style when describing commands: we
always start with a list of the commands with short descriptions,
and follow that by the detailed descriptions.
. I don't understand the rationale for removing the "C-u" and
"C-u C-u" sequences from the short list. What is the purpose of
that?
next prev parent reply other threads:[~2018-09-24 15:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:47 Doc of keyboard macros Stefan Monnier
2018-09-24 15:21 ` Eli Zaretskii [this message]
2018-09-24 15:51 ` Eli Zaretskii
2018-09-24 16:36 ` Stefan Monnier
2018-09-24 16:50 ` Andreas Schwab
2018-09-24 17:07 ` Eli Zaretskii
2018-09-24 19:00 ` Stefan Monnier
2018-09-24 19:23 ` Juri Linkov
2018-09-24 19:35 ` Eli Zaretskii
2018-09-24 20:03 ` Alan Mackenzie
2018-09-24 20:17 ` Joost Kremers
2018-10-10 20:25 ` Mathias Dahl
2018-10-14 8:28 ` Marcin Borkowski
2018-10-14 14:33 ` Yuri Khan
2018-10-15 20:22 ` Juri Linkov
2018-10-16 1:05 ` Van L
2018-09-24 20:06 ` Drew Adams
2018-09-24 20:22 ` Filipp Gunbin
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=835zyuc457.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).