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 13:47:22 -0700 [thread overview]
Message-ID: <56E7235A.8010305@cs.ucla.edu> (raw)
In-Reply-To: <m28u1koo2i.fsf@newartisans.com>
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:
NEWS:66:unless gfile is explicitly requested via
--with-file-notification='gfile'.
NEWS:576:(add-to-list 'display-buffer-alist
NEWS:577: '("^\\*shell\\*$" . (display-buffer-same-window))).
NEWS:639:folding in the middle of a search by typing ‘M-s '’.
NEWS:1458:for straight apostrophes 'like this', and to ‘grave’ for grave
accent
NEWS:1459:and apostrophe `like this'. The default value nil acts like
‘curve’
NEWS:1745:apostrophe `like-this'. The new style looks better on today’s
displays.
NEWS:1747:into documentation by typing ` and '. Outside Electric Quote
mode,
If we use substitute-command-keys (simplest), the above lines would turn
into:
unless gfile is explicitly requested via
--with-file-notification=\='gfile\='.
(add-to-list \='display-buffer-alist
\='("^\\*shell\\*$" . (display-buffer-same-window))).
folding in the middle of a search by typing ‘M-s \='’.
for straight apostrophes \='like this\=', and to `grave' for grave accent
and apostrophe \=`like this\='. The default value nil acts like `curve'
apostrophe \=`like-this\='. The new style looks better on today's displays.
into documentation by typing \=` and \='. Outside Electric Quote mode,
Plus, this line:
before, characters preceded by \= are output as-is.
would need to be changed to this:
before, characters preceded by \=\= are output as-is.
The above would all run afoul of Eli's desire to use other programs to
read etc/NEWS as-is, though.
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.
next prev parent reply other threads:[~2016-03-14 20:47 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 [this message]
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=56E7235A.8010305@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 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.