From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation
Date: Mon, 14 Mar 2016 12:14:04 -0700 [thread overview]
Message-ID: <56E70D7C.9080709@cs.ucla.edu> (raw)
In-Reply-To: <m2pouwoq45.fsf@newartisans.com>
On 03/14/2016 11:45 AM, John Wiegley wrote:
> It would be my preference to use `these quotes' in etc/NEWS, and any other
> text-based internal documentation,
etc/NEWS is not internal documentation, as it gets put on the screen
when one types C-h n. Grave quoting `like this' should not appear in
text meant for users to see.
The "eval: (progn (require 'electric) (electric-quote-local-mode t))"
patch would let you continue to type with grave quoting, as it would
automatically curve the quotes as you type them. As Eli mentioned,
though, enough people view etc/NEWS in non-UTF-8-aware environments that
for this particular file it sounds like we should go back to straight
ASCII for it. Straight quoting 'like this' is the simplest way out,
which is why I did it that way originally.
next prev parent reply other threads:[~2016-03-14 19:14 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
2016-03-14 19:14 ` Paul Eggert [this message]
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
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=56E70D7C.9080709@cs.ucla.edu \
--to=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 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).