From: Alan Mackenzie <acm@muc.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: John Wiegley <johnw@gnu.org>, emacs-devel@gnu.org
Subject: Re: Permission requested to merge branch comment-cache into master.
Date: Sat, 12 Mar 2016 14:06:52 +0000 [thread overview]
Message-ID: <20160312140652.GD2572@acm.fritz.box> (raw)
In-Reply-To: <d472c88f-715b-1a99-53a5-6c9297893724@yandex.ru>
Hello, Dmitry.
On Sat, Mar 12, 2016 at 03:23:45PM +0200, Dmitry Gutov wrote:
> On 03/12/2016 02:28 AM, Alan Mackenzie wrote:
> > Could I merge branch comment-cache into master, please?
> I'm not John, but I wish we didn't hurry so much to merge experimental
> branches into master. The curly quotes feature comes to mind, and how it
> ended up very hard to back out of.
This feature would be easier to remove: changes in 6 C files and some
(two or three) .texi files (not yet done).
> > An alternative approach using the syntax-ppss cache has been discussed
> > and tried. For reasons currently being discussed in bug #22983:
> > (syntax-ppss returns wrong result) and the emacs-devel thread "Problems
> > with syntax-ppss: Was [... Apply `comment-depth' text properties when
> > calling `back_comment'.]", this approach cannot work.
> This seems like a misrepresentation of the discussion in #22983. If
> anything, I'd expect the reverse conclusion: it's quite possible to make
> syntax-ppss stricter, and then base comments-cache on it.
It would require a new function similar to syntax-ppss, but with a
different specification. There are some other issues regarding
syntax-ppss being used in back_comment, too.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-03-12 14:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 0:28 Permission requested to merge branch comment-cache into master Alan Mackenzie
2016-03-12 7:32 ` Eli Zaretskii
2016-03-12 10:08 ` Alan Mackenzie
2016-03-12 11:14 ` Eli Zaretskii
2016-03-12 11:50 ` Alan Mackenzie
2016-03-12 12:31 ` Eli Zaretskii
2016-03-12 13:11 ` Alan Mackenzie
2016-03-12 21:38 ` John Wiegley
2016-03-12 23:17 ` Alan Mackenzie
2016-03-13 0:02 ` John Wiegley
2016-03-13 15:20 ` Alan Mackenzie
2016-03-13 16:04 ` Clément Pit--Claudel
2016-03-13 16:12 ` Dmitry Gutov
2016-03-13 19:12 ` Alan Mackenzie
2016-03-13 22:27 ` Stefan Monnier
2016-03-13 22:52 ` Alan Mackenzie
2016-03-13 23:38 ` Clément Pit--Claudel
2016-03-14 0:20 ` Stefan Monnier
2016-03-14 6:32 ` Andreas Röhler
2016-03-14 11:27 ` Alan Mackenzie
2016-03-13 17:07 ` John Wiegley
2016-03-13 19:04 ` Alan Mackenzie
2016-03-14 0:25 ` Dmitry Gutov
2016-03-14 1:11 ` Stefan Monnier
2016-03-14 13:28 ` Alan Mackenzie
2016-03-14 15:58 ` Stefan Monnier
2016-03-13 18:03 ` Eli Zaretskii
2016-03-12 13:23 ` Dmitry Gutov
2016-03-12 14:06 ` Alan Mackenzie [this message]
2016-03-12 21:39 ` John Wiegley
2016-03-13 17:22 ` Stefan Monnier
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=20160312140652.GD2572@acm.fritz.box \
--to=acm@muc.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=johnw@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.