From: John Wiegley <jwiegley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation
Date: Mon, 14 Mar 2016 11:45:30 -0700 [thread overview]
Message-ID: <m2pouwoq45.fsf@newartisans.com> (raw)
In-Reply-To: <56E703D9.8000607@cs.ucla.edu> (Paul Eggert's message of "Mon, 14 Mar 2016 11:32:57 -0700")
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
>>>>> Paul Eggert <eggert@cs.ucla.edu> writes:
> Alternatively we could revert commit
> 4235d2d9eaa3b64d3172f6c60f1e71704795af89 and go back to straight quoting
> 'like this' in etc/NEWS, as was done after my first patch today. That would
> be adequate too, even though (as John said) it is less consistent with the
> rest of the documentation. The main point is that grave quoting `like this'
> is not right in user-facing documentation.
It would be my preference to use `these quotes' in etc/NEWS, and any other
text-based internal documentation, rather than try to use curly quotes
everywhere. It sounds like the preference of a lot of other people as well, in
addition to its being easier to maintain, so let's revert that commit and go
back to `quotes'.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-03-14 18:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160314154123.2684.74715@vcs.savannah.gnu.org>
[not found] ` <E1afUcV-0000iS-4N@vcs.savannah.gnu.org>
2016-03-14 15:44 ` [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation John Wiegley
2016-03-14 16:31 ` Paul Eggert
2016-03-14 16:39 ` John Wiegley
2016-03-14 16:42 ` Dmitry Gutov
2016-03-14 17:19 ` Clément Pit--Claudel
2016-03-14 17:37 ` Dmitry Gutov
2016-03-14 17:53 ` Kaushal Modi
2016-03-14 18:10 ` Drew Adams
2016-03-14 18:32 ` Paul Eggert
2016-03-14 18:43 ` Eli Zaretskii
2016-03-14 18:48 ` John Wiegley
2016-03-14 18:58 ` Eli Zaretskii
2016-03-14 18:45 ` John Wiegley [this message]
2016-03-14 19:14 ` Paul Eggert
2016-03-14 19:29 ` John Wiegley
2016-03-14 20:47 ` Paul Eggert
2016-03-14 20:50 ` John Wiegley
2016-03-15 0:30 ` Paul Eggert
2016-03-15 22:21 ` John Wiegley
2016-03-15 23:13 ` Lars Magne Ingebrigtsen
2016-03-15 23:56 ` Drew Adams
2016-03-16 0:11 ` Paul Eggert
2016-03-16 0:52 ` Drew Adams
2016-03-16 8:16 ` John Wiegley
2016-03-16 17:55 ` Paul Eggert
2016-03-16 21:26 ` Drew Adams
2016-03-16 23:37 ` Paul Eggert
2016-03-16 23:41 ` Drew Adams
2016-03-14 20:56 ` Alan Mackenzie
2016-03-15 0:39 ` Paul Eggert
2016-03-14 18:50 ` Kaushal Modi
2016-03-14 19:11 ` Dmitry Gutov
2016-03-14 19:16 ` Drew Adams
2016-03-14 19:39 ` John Wiegley
2016-03-14 19:47 ` Dmitry Gutov
2016-03-14 17:03 ` Eli Zaretskii
2016-03-14 18:24 ` Paul Eggert
2016-03-14 18:42 ` Eli Zaretskii
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=m2pouwoq45.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.