From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation
Date: Mon, 14 Mar 2016 20:56:21 +0000 [thread overview]
Message-ID: <20160314205621.GI1894@acm.fritz.box> (raw)
In-Reply-To: <56E7235A.8010305@cs.ucla.edu>
Hello, Paul.
On Mon, Mar 14, 2016 at 01:47:22PM -0700, Paul Eggert wrote:
> On 03/14/2016 12:29 PM, John Wiegley wrote:
> > Could we render the quotes the way that we currently do for Elisp
> > documentation?
> Yes, that could be done. We'd need an escape mechanism for the rare
> cases where quotes should not be replaced, as in the following lines:
Please don't do that. NEWS is a text file, not a markup file. It
should remain readable with "anything".
[ .... ]
> The above would all run afoul of Eli's desire to use other programs to
> read etc/NEWS as-is, though.
Mine, too.
> I'm afraid that straight quoting 'like this' is the simplest way out of
> this mess. It is not a great solution, but it is the simplest and the
> other approaches all have problems that may be worse. This is why the
> patch I originally installed today used straight quoting. How about if
> we simply go back to it? I.e., revert commit
> 4235d2d9eaa3b64d3172f6c60f1e71704795af89 and then move on.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-03-14 20:56 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
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 [this message]
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=20160314205621.GI1894@acm.fritz.box \
--to=acm@muc.de \
--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 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).