From: Dmitry Gutov <dgutov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master c4151eb: Improve the optional translation of quotes
Date: Sun, 21 Jun 2015 23:29:10 +0300 [thread overview]
Message-ID: <55871E96.2020506@yandex.ru> (raw)
In-Reply-To: <55871883.7080600@cs.ucla.edu>
On 06/21/2015 11:03 PM, Paul Eggert wrote:
> We've had non-ASCII strings in GNU Emacs Lisp source-code strings for
> several years. It hasn't been a problem in practice. Obviously we
> can't use any Unicode character willy-nilly in any context, but it's
> quite safe now to use curved single quotes in docstrings.
Okay, rather than ASCII or not in Elisp code, my concern is whether
`substitute-command-keys' should translate *from* curved quotes. It's
not hard to imagine `substitute-command-keys' being called on its result
again, and then there will be risk of matching different pairs or quotes.
I'd rather keep them in the destination strings, if at all. Like
mentioned in the other thread, we can switch to simply using a face to
highlight code segments, and then the curved quotes won't be needed at
all (at least if that's the user's preference).
Regarding the GC argument, I think you'll be hard-pressed to find a
machine where it'll make a noticeable difference when processing
read-life docstrings.
next prev parent reply other threads:[~2015-06-21 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150619073901.5856.32718@vcs.savannah.gnu.org>
[not found] ` <E1Z5qtC-0001Xe-1y@vcs.savannah.gnu.org>
2015-06-21 19:09 ` [Emacs-diffs] master c4151eb: Improve the optional translation of quotes Dmitry Gutov
2015-06-21 19:56 ` Paul Eggert
2015-06-21 19:57 ` Dmitry Gutov
2015-06-21 20:03 ` Paul Eggert
2015-06-21 20:29 ` Dmitry Gutov [this message]
2015-06-21 20:46 ` Paul Eggert
2015-06-21 23:52 ` Dmitry Gutov
2015-06-22 6:50 ` Paul Eggert
2015-06-22 15:09 ` Dmitry Gutov
2015-06-23 5:36 ` Paul Eggert
2015-06-23 10:55 ` Dmitry Gutov
2015-06-24 5:24 ` Paul Eggert
2015-06-25 12:52 ` Dmitry Gutov
2015-06-25 14:05 ` Paul Eggert
2015-06-25 14:56 ` Dmitry Gutov
2015-07-31 18:51 ` Paul Eggert
2015-07-31 19:24 ` Dmitry Gutov
2015-08-01 1:16 ` Paul Eggert
2015-08-01 1:28 ` Dmitry Gutov
2015-06-25 14:59 ` Dmitry Gutov
2015-06-25 15:11 ` Eli Zaretskii
2015-06-25 15:33 ` Dmitry Gutov
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=55871E96.2020506@yandex.ru \
--to=dgutov@yandex.ru \
--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).