From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Alan Mackenzie <acm@muc.de>, 23425@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#23425: master branch: `message' wrongly corrupts ' to curly quote.
Date: Mon, 05 Jun 2017 20:31:14 +0200 [thread overview]
Message-ID: <87k24qgubx.fsf__17936.5320866511$1496687532$gmane$org@linux-m68k.org> (raw)
In-Reply-To: <ac90b979-6a37-29c4-03b3-6322ac2cc11a@cs.ucla.edu> (Paul Eggert's message of "Mon, 5 Jun 2017 11:19:06 -0700")
On Jun 05 2017, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Suppose the same string is used for both messages and
> documentation. You're proposing %` in the former where ` is in the latter,
> so we would need distinct strings.People cut and paste between messages
> and doc strings, and it's possible there's even code that does this (I
> haven't checked). Using different quoting notations for the two kinds of
> strings will cause confusion and problems.
That's a bad argument. A doc string already has completely different
special characters.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-06-05 18:31 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 14:55 bug#23425: master branch: `message' wrongly corrupts ' to curly quote Alan Mackenzie
2016-05-02 16:25 ` Lars Ingebrigtsen
2016-05-02 16:41 ` Drew Adams
2016-05-02 17:53 ` Paul Eggert
2016-05-02 19:10 ` Alan Mackenzie
2016-05-03 15:17 ` Paul Eggert
2016-05-03 16:36 ` Drew Adams
2016-05-03 16:59 ` Eli Zaretskii
2016-05-03 15:38 ` Eli Zaretskii
2016-05-03 16:27 ` Alan Mackenzie
2016-05-03 16:55 ` Eli Zaretskii
2016-05-03 20:03 ` Alan Mackenzie
2016-05-03 20:49 ` Paul Eggert
2016-05-04 15:32 ` Eli Zaretskii
2016-05-04 16:48 ` Alan Mackenzie
2016-05-04 17:03 ` Eli Zaretskii
2016-05-04 17:37 ` Josh
2016-05-04 19:05 ` Eli Zaretskii
2016-05-04 18:04 ` Alan Mackenzie
2016-05-04 18:39 ` Paul Eggert
2016-05-04 18:57 ` Alan Mackenzie
2016-05-04 19:02 ` John Wiegley
2016-05-04 21:34 ` Paul Eggert
2016-05-04 21:50 ` Paul Eggert
2016-05-04 23:49 ` Paul Eggert
2016-05-05 15:51 ` Eli Zaretskii
2016-05-10 14:41 ` Paul Eggert
2017-05-31 1:07 ` Glenn Morris
2017-05-31 1:42 ` Paul Eggert
2017-05-31 21:24 ` Alan Mackenzie
2017-05-31 23:26 ` Paul Eggert
2017-06-02 21:02 ` Alan Mackenzie
2017-06-02 21:15 ` Dmitry Gutov
2017-06-03 21:10 ` Alan Mackenzie
[not found] ` <20170603211010.GD2130@acm.fritz.box>
2017-06-03 21:32 ` Dmitry Gutov
2017-06-02 21:47 ` Paul Eggert
2017-06-03 0:13 ` Glenn Morris
2017-06-03 21:01 ` Alan Mackenzie
2017-06-03 20:53 ` Alan Mackenzie
[not found] ` <20170603205331.GA2130@acm.fritz.box>
2017-06-04 21:01 ` Paul Eggert
2017-06-05 16:27 ` Alan Mackenzie
[not found] ` <20170605162737.GA30946@acm.fritz.box>
2017-06-05 18:19 ` Paul Eggert
[not found] ` <ac90b979-6a37-29c4-03b3-6322ac2cc11a@cs.ucla.edu>
2017-06-05 18:31 ` Andreas Schwab [this message]
2017-06-05 20:37 ` Alan Mackenzie
[not found] ` <20170605203753.GB30946@acm.fritz.box>
2017-06-05 21:05 ` Clément Pit-Claudel
2017-06-07 16:50 ` Alan Mackenzie
2017-06-07 19:29 ` Clément Pit-Claudel
2017-06-06 0:14 ` Paul Eggert
2017-06-06 8:21 ` Andreas Schwab
[not found] ` <mvmtw3tsf05.fsf@suse.de>
2017-06-06 12:24 ` Clément Pit-Claudel
[not found] ` <fa92f34f-982b-e9a5-be21-188e694e38d9@gmail.com>
2017-06-06 13:55 ` Yuri Khan
[not found] ` <CAP_d_8X7V_G4g7emn_EPd_YYPKu2HfnDE+Q3FOPMGXpB4sEYSw@mail.gmail.com>
2017-06-06 18:21 ` Clément Pit-Claudel
2017-06-06 18:59 ` Yuri Khan
[not found] ` <CAP_d_8X5OBsQQ=0+dj-qYFV3yEC4WZVMpyRw1KyiM0tvJUNFMw@mail.gmail.com>
2017-06-06 19:39 ` Clément Pit-Claudel
[not found] ` <10515b89-1c60-227e-ff3d-3127f59c0daf@gmail.com>
2017-06-07 4:57 ` Eli Zaretskii
2017-06-06 23:09 ` Paul Eggert
2017-06-07 7:44 ` Andreas Schwab
2017-06-07 18:17 ` Paul Eggert
2017-06-08 8:04 ` Andreas Schwab
2017-06-07 13:27 ` Drew Adams
2017-06-07 19:13 ` Alan Mackenzie
2017-06-07 19:27 ` Clément Pit-Claudel
[not found] ` <966db090-4aa1-231c-ef5a-370ece8905d1@gmail.com>
2017-06-07 19:33 ` Dmitry Gutov
2017-06-07 19:51 ` Alan Mackenzie
2017-06-07 20:33 ` Alan Mackenzie
2017-06-07 23:28 ` Paul Eggert
2017-06-08 17:34 ` Alan Mackenzie
2017-06-08 20:17 ` Paul Eggert
2017-06-09 19:41 ` Alan Mackenzie
2017-06-09 20:17 ` Drew Adams
2017-06-09 20:38 ` Alan Mackenzie
2017-06-09 21:05 ` Drew Adams
2017-06-09 21:44 ` Paul Eggert
2017-06-09 22:51 ` Drew Adams
2017-06-10 0:20 ` Paul Eggert
2017-06-10 10:01 ` Alan Mackenzie
2017-06-10 10:52 ` David Engster
2017-06-10 11:48 ` Eli Zaretskii
2017-06-10 13:01 ` Alan Mackenzie
2017-06-10 13:39 ` Eli Zaretskii
2017-06-11 10:03 ` Alan Mackenzie
2017-06-11 14:37 ` Eli Zaretskii
2017-06-10 15:28 ` Dmitry Gutov
2017-06-01 16:56 ` Glenn Morris
2017-06-03 21:07 ` Alan Mackenzie
2016-05-04 18:46 ` John Wiegley
2016-05-04 20:23 ` Dmitry Gutov
2016-05-04 21:15 ` John Wiegley
2016-05-04 22:19 ` Lars Ingebrigtsen
2016-05-05 7:12 ` Andreas Schwab
2016-05-05 17:05 ` Eli Zaretskii
2016-05-05 8:06 ` Alan Mackenzie
2016-05-05 17:06 ` Eli Zaretskii
2016-05-05 23:46 ` John Wiegley
2016-05-06 8:54 ` Nicolas Petton
2016-05-04 19:08 ` Eli Zaretskii
2016-05-04 21:49 ` Andreas Schwab
2017-06-09 20:31 ` Glenn Morris
2017-06-10 7:08 ` 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='87k24qgubx.fsf__17936.5320866511$1496687532$gmane$org@linux-m68k.org' \
--to=schwab@linux-m68k.org \
--cc=23425@debbugs.gnu.org \
--cc=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).