From: Dmitry Gutov <dgutov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: A simple solution to "Upcoming loss of usability ..."
Date: Sat, 27 Jun 2015 20:53:25 +0300 [thread overview]
Message-ID: <558EE315.3080107@yandex.ru> (raw)
In-Reply-To: <558EDD4C.4040002@cs.ucla.edu>
On 06/27/2015 08:28 PM, Paul Eggert wrote:
> In that case I don't understand the patch being against f743819.
> f743819 already has some curved quotes in docstrings, to avoid
> ambiguities of using grave accent and apostrophe to quote. So that
> patch against f743819 won't determine whether font-lock can address this
> issue without using curved quotes in docstrings.
I just needed a version where substitute-command-keys doesn't replace
the quotes (so that the font-lock rules do have something to work on).
The question of ambiguity is a matter of refining the patch.
> Even with this in mind, though, the patch mishandles some quotes. For
> example, the docstring for texinfo-format-verb contains:
>
> For example, @verb\{|@|\} results in @ and
> @verb\{+@'e?`!`+} results in @'e?`!`.
>
> The patch displays this as:
>
> For example, @verb{|@|} results in @ and
> @verb{+@'e?`!‘+} results in @’e?`!`.
>
> which is incorrect: those curved quotes should be grave accent and
> apostrophe.
Only because the regexp is constructed this way, and we haven't picked
an escaping syntax.
> It'd be impractical to work around this sort of problem entirely with
> clever font-lock regular expressions. We will need some escape syntax
> to suppress transliteration for exceptional docstrings like the above.
> I think you've mentioned the need for that sort of thing, but it's not
> clear what it would look like or
I've described the possible options in the previous message here of this
subthread (in the second half):
http://lists.gnu.org/archive/html/emacs-devel/2015-06/msg00592.html
So, do you find "\\" acceptable? Should I send a patch with support for it?
> how it would be implemented with font-lock.
There are several examples in our Lisp code of searching for only
unescaped instances of some character, using a regexp. But failing that,
examining characters preceding a match would work almost as well.
> Plus, as we've mentioned, the patch can mishandle user-supplied values
> that contain grave accent and apostrophe.
Nothing surprising there either. I'll try to handle it in the next
version of the patch.
>> It will be very easy to limit the conversion to only within strings.
>
> As I understand it we gave up on transliteration of Elisp source code
> after you wrote the above, so for now I'll not comment on this point (or
> the other points of the message that talk about transliterating source
> code).
You have also snipped the suggestions about the escaping syntax.
>> Is Info actually relevant in this discussion? Looking at info.el, it
>> seems to
>
> It's relevant, as it uses and displays the curved quotes that some users
> find objectionable, and did so even in 24.5.
I thought the external program performs the conversion. But yes,
converting those curly quotes to straight ones in font-lock is also
possible.
next prev parent reply other threads:[~2015-06-27 17:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 14:59 A simple solution to "Upcoming loss of usability ..." Oleh Krehel
2015-06-25 15:37 ` Dmitry Gutov
2015-06-25 16:36 ` Paul Eggert
2015-06-25 17:00 ` Oleh Krehel
2015-06-25 20:48 ` Paul Eggert
2015-06-25 21:10 ` Dmitry Gutov
2015-06-25 22:15 ` Paul Eggert
2015-06-25 22:25 ` Dmitry Gutov
2015-06-25 22:41 ` Paul Eggert
2015-06-25 22:52 ` Dmitry Gutov
2015-06-27 15:00 ` raman
2015-06-25 18:32 ` Dmitry Gutov
2015-06-25 22:17 ` Paul Eggert
2015-06-25 22:38 ` Dmitry Gutov
2015-06-26 2:35 ` Paul Eggert
2015-06-26 12:06 ` Dmitry Gutov
2015-06-27 17:28 ` Paul Eggert
2015-06-27 17:53 ` Dmitry Gutov [this message]
2015-06-27 21:09 ` Paul Eggert
2015-06-28 1:04 ` Dmitry Gutov
2015-06-28 15:20 ` Paul Eggert
2015-06-28 20:27 ` Escaping quotes in docstrings, Was: " Dmitry Gutov
2015-06-28 23:29 ` Dmitry Gutov
2015-07-01 2:56 ` Paul Eggert
2015-07-02 0:09 ` Dmitry Gutov
2015-07-02 6:57 ` Paul Eggert
2015-07-02 9:46 ` Dmitry Gutov
2015-07-06 6:12 ` Paul Eggert
2015-07-06 12:07 ` Dmitry Gutov
2015-07-06 16:30 ` Paul Eggert
2015-07-06 22:10 ` Dmitry Gutov
2015-07-07 7:54 ` Paul Eggert
2015-07-07 8:39 ` Dmitry Gutov
2015-08-01 1:36 ` Paul Eggert
2015-08-01 21:05 ` Dmitry Gutov
2015-08-02 6:56 ` Paul Eggert
2015-08-02 12:51 ` Dmitry Gutov
2015-08-02 15:13 ` Paul Eggert
2015-08-02 18:31 ` Dmitry Gutov
2015-08-02 8:49 ` Przemysław Wojnowski
2015-08-02 19:16 ` Drew Adams
2015-06-27 17:57 ` Dmitry Gutov
2015-06-25 23:12 ` João Távora
2015-06-26 7:40 ` Oleh Krehel
2015-06-26 14:54 ` Paul Eggert
2015-06-26 15:03 ` Dmitry Gutov
2015-06-25 20:58 ` Alan Mackenzie
2015-06-25 22:34 ` Paul Eggert
2015-06-25 22:40 ` Dmitry Gutov
2015-06-25 22:45 ` Paul Eggert
2015-06-25 22:55 ` 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=558EE315.3080107@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).