From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Gutov <dgutov@yandex.ru>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 9d35bb8: Fix minor quoting problems in doc strings
Date: Tue, 19 May 2015 19:14:41 -0700 [thread overview]
Message-ID: <555BEE11.3020300@cs.ucla.edu> (raw)
In-Reply-To: <555BE07E.8090209@yandex.ru>
Dmitry Gutov wrote:
> Those two cases look simple (replace ` and the first matching ', the second `
> would be skipped),
That would do the wrong thing in other places. We have doc strings with stuff
like this:
This is like `(let ((v ,EXP)) ,EXPS) except that `v' is a new generated
which is why I'm leery about allowing ` within strings quoted `like this'.
> but if the apostrophe were quoted, it'd have to be escaped: `\''.
Which means the source would have to say "`\\''" and the backslash would have to
be removed before showing the result to the user.
> And it's not very simple, but a regular expression can distinguish between an
> escaped and an unescaped character.
Ouch! Let's keep things simple if we can.
> Not a big deal indeed, but consistency would be preferable IMHO.
OK, I installed commit f743819b57ef519109c1b9d520d358d19a197086 to do that.
next prev parent reply other threads:[~2015-05-20 2:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150519220123.30678.22605@vcs.savannah.gnu.org>
[not found] ` <E1YupZj-000803-T3@vcs.savannah.gnu.org>
2015-05-19 22:30 ` [Emacs-diffs] master 9d35bb8: Fix minor quoting problems in doc strings Dmitry Gutov
2015-05-19 23:18 ` Paul Eggert
2015-05-20 1:16 ` Dmitry Gutov
2015-05-20 2:14 ` Paul Eggert [this message]
2015-05-20 2:36 ` Dmitry Gutov
2015-05-20 2:45 ` Dmitry Gutov
2015-05-20 2:49 ` Paul Eggert
2015-05-20 12:25 ` Dmitry Gutov
2015-05-20 12:50 ` Stefan Monnier
2015-05-21 7:36 ` Paul Eggert
2015-05-21 10:05 ` Dmitry Gutov
2015-05-21 14:44 ` Paul Eggert
2015-05-20 4:23 ` Yuri Khan
2015-05-20 15:36 ` Glenn Morris
2015-05-21 5:18 ` Paul Eggert
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=555BEE11.3020300@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dgutov@yandex.ru \
--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.