all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 23 Jun 2015 13:55:41 +0300	[thread overview]
Message-ID: <55893B2D.40506@yandex.ru> (raw)
In-Reply-To: <5588F071.7030501@cs.ucla.edu>

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	other threads:[~2015-06-23 10:55 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55893B2D.40506@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 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.