From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 45536@debbugs.gnu.org
Subject: bug#45536: [PATCH] Pretty-print keys without <> around modifiers
Date: Thu, 31 Dec 2020 05:35:43 +0100 [thread overview]
Message-ID: <87im8ioan4.fsf@gnus.org> (raw)
In-Reply-To: <97ADE294-0674-4CAC-96B1-DAD947BA3A32@acm.org> ("Mattias Engdegård"'s message of "Wed, 30 Dec 2020 10:52:37 +0100")
Mattias Engdegård <mattiase@acm.org> writes:
> Let me give you a hand then! The latest patch puts the change under
> control of a variable, defaulting to off. This should take care of
> your concerns for compatibility problems, as well as the possibility
> of confusion (which I think is minuscule).
The confusion problem is still present, though -- people will see
different ways of representing keystrokes (in examples on the web,
etc).
> The variable can be set permanently by users who prefer the new key
> binding style. It can also be bound temporarily for specific uses. It
> was a specific use I had in mind, but there is no reason to withhold
> an improvement from users in general.
What's the specific use case?
> Thanks for your careful reasoning. We can all agree that if we
> included pleasing everybody on Reddit in our design criteria, no
> progress would ever be made.
I wasn't worried about pleasing anybody -- I just want to avoid
unnecessary confusion.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-31 4:35 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 [this message]
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
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=87im8ioan4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45536@debbugs.gnu.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).