From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: larsi@gnus.org, 45536@debbugs.gnu.org
Subject: bug#45536: [PATCH] Pretty-print keys without <> around modifiers
Date: Fri, 01 Jan 2021 14:28:16 +0200 [thread overview]
Message-ID: <83tus0g7tr.fsf@gnu.org> (raw)
In-Reply-To: <020D0443-20C2-4F8B-81FE-F1040469E919@acm.org> (message from Mattias Engdegård on Fri, 1 Jan 2021 13:10:28 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 1 Jan 2021 13:10:28 +0100
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45536@debbugs.gnu.org
>
> 1 jan. 2021 kl. 13.00 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > What the manual uses is the format makeinfo emits for keys and key
> > sequences in the Info format. It is only very loosely related to the
> > way we format key sequences in Emacs.
>
> But it is what users see when they read the manual in Info, so clearly they cannot be surprised or confused by it.
The users also see that in Info manuals that have nothing to do with
Emacs, so their surprise, if it exists, is misguided, and if they use
what's in the manual to request that Emacs behaves the same, those
requests are misdirected.
Besides, your suggested changes don't produce results that are 100%
identical with what's in Info manuals, either, so how would you
explain the differences to those users?
> When the manual seeks to make an explicit example (with '<' instead of @key), it uses the logical style as well. See the examples used to illustrate the manual entry for the 'kbd' function itself.
That's the tiny minority of the examples you show, most of them are
unrelated to 'kbd'.
next prev parent reply other threads:[~2021-01-01 12:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 16:21 bug#45536: [PATCH] Pretty-print keys without <> around modifiers Mattias Engdegård
2020-12-29 18:31 ` Drew Adams
2020-12-29 19:50 ` Mattias Engdegård
2020-12-29 20:14 ` Drew Adams
2020-12-29 20:01 ` Eli Zaretskii
2020-12-29 22:27 ` Mattias Engdegård
2020-12-30 3:54 ` Lars Ingebrigtsen
2020-12-30 9:52 ` Mattias Engdegård
2020-12-31 4:35 ` Lars Ingebrigtsen
2020-12-31 9:59 ` Mattias Engdegård
2020-12-31 12:29 ` Mattias Engdegård
2021-01-01 10:46 ` Lars Ingebrigtsen
2021-01-01 11:51 ` Mattias Engdegård
2021-01-01 11:54 ` Lars Ingebrigtsen
2021-01-02 17:20 ` Mattias Engdegård
2021-01-02 18:25 ` Drew Adams
2021-01-05 10:52 ` Mattias Engdegård
2021-01-05 10:47 ` Mattias Engdegård
2021-05-17 15:11 ` Lars Ingebrigtsen
2021-01-01 12:00 ` Eli Zaretskii
2021-01-01 12:10 ` Mattias Engdegård
2021-01-01 12:28 ` Eli Zaretskii [this message]
2021-01-01 12:43 ` Mattias Engdegård
2021-01-01 12:54 ` Eli Zaretskii
2021-01-01 13:29 ` Mattias Engdegård
2021-01-01 13:34 ` Eli Zaretskii
2021-01-01 19:41 ` 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
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=83tus0g7tr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45536@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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).