unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 5b1109394c: ; * lisp/edmacro.el: Minor doc fixes.
Date: Thu, 23 Jun 2022 08:43:11 +0300	[thread overview]
Message-ID: <83a6a4exzk.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmn5TXT2mRvwWKAg5E-1=G394VdeVpCKkX+Sy7oe-ew=BQ@mail.gmail.com> (message from Stefan Kangas on Wed, 22 Jun 2022 22:17:45 +0200)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 22 Jun 2022 22:17:45 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Stefan, I don't understand this change.  Is it no longer "kosher" to
> > use RET, TAB, SPC, etc. in our doc strings?  Why do we need to quote
> > these simple keys?
> 
> The reason for fontifying them is consistency, so that keybindings are
> always displayed the same in *Help*.
> 
> AFAIU, such consistency is important for effective UX design.

Again, that's not what I asked.  I asked whether _all_ references to
these keys in doc strings should be quoted.  If the answer is YES, I
guess that means we will soon see changes to that effect all over the
place in the existing code, and we should comment on patches which
don't do that to tell the contributors to do so.  Right?



  reply	other threads:[~2022-06-23  5:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 14:05 master 5b1109394c: ; * lisp/edmacro.el: Minor doc fixes Eli Zaretskii
2022-06-22 14:26 ` Lars Ingebrigtsen
2022-06-22 15:57   ` Eli Zaretskii
2022-06-22 20:17 ` Stefan Kangas
2022-06-23  5:43   ` Eli Zaretskii [this message]
2022-06-23  9:15     ` Stefan Kangas

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=83a6a4exzk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    /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).