[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] master c4151eb: Improve the optional translation of qu

From: Dmitry Gutov
Subject: Re: [Emacs-diffs] master c4151eb: Improve the optional translation of quotes
Date: Tue, 23 Jun 2015 13:55:41 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0

On 06/23/2015 08:36 AM, Paul Eggert wrote:

Yes, and we have that now.  The simplest way to use it is to use the
same curved quotes in input as in output, but we can add more complex
ways as needed.

It may look easiest, but I wouldn't call it "simplest". It would be better to have a clear separation between the input and output. If you don't like the `' quotes so much, why not borrow a quoting method from some other popular markup language, like tildes from org?

For the other options, see "fixed width text" in http://hyperpolyglot.org/lightweight-markup.

Of course.  Font-lock is pretty much independent of the quoting
mechanism that docstrings use.

That's not true. For better results, font-lock will need to handle the escaping and quote conversion.

Otherwise, it won't know whether a given character was escaped in the docstring, or was present there verbatim.

 For example, if we decide to support
only backslash escapes to quote in docstrings (yuck!), we could get that
to work with font-lock; or if we decide to support only curved quotes to
quote in docstrings (too aggressive, if you ask me), we could get that
to work with font-lock too.

When I tried font-lock mode in this area I came away baffled (see
Bug#20385 Message#289, and Bug#20613), so I don't know how well it'd
really work in practice for this problem.  It is a poorly documented
area, unfortunately.

I gave you a recipe for a fix in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20385#292, and it worked fine for me locally. (I thought I've also sent a patch, but apparently not).

So if you had trouble applying that, maybe you should've asked for the proper patch instead of rushing the other way.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]