From: Paul Eggert <eggert@cs.ucla.edu>
To: David Kastrup <dak@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dgutov@yandex.ru, emacs-devel@gnu.org, rms@gnu.org,
"T.V Raman" <raman@google.com>
Subject: Re: Please stop putting curly quotes into doc strings!
Date: Thu, 10 Sep 2015 10:25:59 -0700 [thread overview]
Message-ID: <55F1BD27.7030802@cs.ucla.edu> (raw)
In-Reply-To: <87k2ry6zvq.fsf@fencepost.gnu.org>
On 09/10/2015 08:46 AM, David Kastrup wrote:
> outcommented stuff that would become non-standard when commented back
Thanks, I missed those, since I didn’t look at comments. Fixed.
> Comments and messages like
Thanks, I missed those message instances, as somebody else introduced
those curved quotes and I looked only at the curved quotes I
introduced. I changed them to use grave quotes just now.
It’s OK to use curved quotes in English text in comments.
> Well, various text files
It’s OK for English text in text files to use curved quotes. In
etc/PROBLEMS, the text is showing an Emacs diagnostic as presented to
the user. This normally uses curved quotes nowadays, so curved quotes
are preferable there. The other curved quotes you mention also look OK.
> various messages like
Those messages generate info files, which typically use curved quotes
nowadays, so curved quotes are appropriate there.
> The English adventure "dunnet"
Please feel free to go through dunnet and change it to use
substitute-command-keys or format-message so that it generates grave
quotes for dunnet users who prefer that style. I did not think it worth
bothering about, myself.
next prev parent reply other threads:[~2015-09-10 17:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 1:14 Please stop putting curly quotes into doc strings! Richard Stallman
2015-09-05 1:40 ` Dmitry Gutov
2015-09-06 2:59 ` Richard Stallman
2015-09-06 4:48 ` Paul Eggert
2015-09-06 5:05 ` Drew Adams
2015-09-06 7:15 ` Zack Piper
2015-09-06 7:16 ` Zack Piper
2015-09-06 7:06 ` Dmitry Gutov
2015-09-06 17:40 ` raman
2015-09-06 19:59 ` Kaushal Modi
2015-09-07 1:25 ` Richard Stallman
2015-09-07 23:17 ` Paul Eggert
2015-09-08 2:24 ` Richard Stallman
2015-09-08 13:00 ` Dmitry Gutov
2015-09-08 13:58 ` Paul Eggert
2015-09-08 16:20 ` raman
2015-09-08 17:00 ` Drew Adams
2015-09-08 22:23 ` Dmitry Gutov
2015-09-08 23:58 ` Paul Eggert
2015-09-09 15:27 ` raman
2015-09-09 17:50 ` Stefan Monnier
2015-09-09 19:55 ` T.V Raman
2015-09-09 22:24 ` Paul Eggert
2015-09-10 3:28 ` Stefan Monnier
2015-09-10 7:55 ` David Kastrup
2015-09-10 15:12 ` Stefan Monnier
2015-09-10 15:46 ` David Kastrup
2015-09-10 17:25 ` Paul Eggert [this message]
2015-09-14 9:27 ` David Kastrup
2015-09-14 15:30 ` T.V Raman
2015-09-08 15:37 ` raman
2015-09-05 3:20 ` Paul Eggert
2015-09-06 2:59 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F1BD27.7030802@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dak@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.com \
--cc=rms@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.