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: Fri, 31 Jul 2015 22:24:05 +0300 [thread overview]
Message-ID: <55BBCB55.1080400@yandex.ru> (raw)
In-Reply-To: <55BBC3B8.4080705@cs.ucla.edu>
On 07/31/2015 09:51 PM, Paul Eggert wrote:
> "Demand" is a pretty strong word. I did ask for better documentation in
> Bug#20613. I realize it's not always easy to write good documentation.
I thought I addressed that bug report more or less adequately.
The piece of code you've quoted does not follow the idiomatic way
font-lock-keywords should be used, but it plays by the documented rules,
and simply adds compose-region as a side-effect. We can't document every
way people might want to write a Lisp program.
In any case, I thought we've moved away from the idea of using
font-lock, to translating the buffer contents directly, in Lisp?
next prev parent reply other threads:[~2015-07-31 19:24 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
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 [this message]
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=55BBCB55.1080400@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.