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:54:46 +0200 [thread overview]
Message-ID: <83pn2og6ll.fsf@gnu.org> (raw)
In-Reply-To: <50C39303-B054-4E6E-9F6E-273794587B8E@acm.org> (message from Mattias Engdegård on Fri, 1 Jan 2021 13:43:17 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 1 Jan 2021 13:43:17 +0100
> Cc: larsi@gnus.org, 45536@debbugs.gnu.org
>
> > 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?
>
> Why do they have to be 100 % identical?
Because you use the differences that exist now as argument for the
change you proposed. If the differences between what we have in Info
and what we have in describe-key are not important, then let's stop
using what the Info manual shows in this discussion.
> Naturally I shall perform any corrections necessary in the documentation. As we have seen, this will not be much work.
What do you mean? The way @key and @kbd are rendered in an Info
manual are completely outside our control.
> > That's the tiny minority of the examples you show, most of them are
> > unrelated to 'kbd'.
>
> Which was precisely my point. The vast majority uses something like C-@key{...}. No change required here.
But @key doesn't produce what your changes will produce, not exactly
anyway. So why we are talking about @key as something related to the
issue at hand?
next prev parent reply other threads:[~2021-01-01 12:54 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
2021-01-01 12:43 ` Mattias Engdegård
2021-01-01 12:54 ` Eli Zaretskii [this message]
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=83pn2og6ll.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).