From: Dmitry Gutov <dgutov@yandex.ru>
To: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: A proposal for the future of open-paren-in-column-0-is-defun-start.
Date: Mon, 6 Apr 2020 22:08:20 +0300 [thread overview]
Message-ID: <a1ab74ae-8c34-0068-00c6-e3ebdf376b79@yandex.ru> (raw)
In-Reply-To: <20200405134735.GD5049@ACM>
Hi Alan,
On 05.04.2020 16:47, Alan Mackenzie wrote:
> `syntax-open-paren-in-literal' would be applied throughout the buffer
> when it is first loaded into Emacs, and would be kept up to date by
> "super before/after-change-functions". (These functions would be called
> at buffer changes regardless of the value of inhibit-modification-hooks.
> We would want some way of inhibiting them being called on a change of
> text properties, for efficiency's sake).
>
> With this mechanism in place, o-p-i-c-0-i-d-s could safely be left
> enabled, for speed's sake, without causing the all too familiar bugs in
> CC Mode.
>
> What do people think?
While I'm not convinced that syntax-ppss is a significant bottleneck
now, nor crazy about the idea of yet another kind of hooks which will
have to scan the whole buffer after every buffer change, I say go for
it. :-)
The proposed approach seems easy enough to implement, and then you could
do some real-world benchmarks (something like: 1. scrolling 50 times, 2.
typing new code in a big file, 3. simply visiting a big file), compare
and see what improved, and what didn't, and by how much. Then we'd have
something to discuss, at least.
next prev parent reply other threads:[~2020-04-06 19:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:47 A proposal for the future of open-paren-in-column-0-is-defun-start Alan Mackenzie
2020-04-05 14:33 ` Stefan Monnier
2020-04-05 15:23 ` Alan Mackenzie
2020-04-05 18:39 ` Stefan Monnier
2020-04-06 2:37 ` Richard Stallman
2020-04-06 15:40 ` Stefan Monnier
2020-04-06 16:04 ` Eli Zaretskii
2020-04-06 16:25 ` Stefan Monnier
2020-04-06 16:36 ` Eli Zaretskii
2020-04-06 17:49 ` Stefan Monnier
2020-04-06 18:16 ` Eli Zaretskii
2020-04-06 18:32 ` andres.ramirez
2020-04-07 8:33 ` martin rudalics
2020-04-07 13:47 ` Stefan Monnier
2020-04-07 14:06 ` Eli Zaretskii
2020-04-06 19:08 ` Dmitry Gutov [this message]
2020-04-06 21:42 ` Stefan Monnier
2020-04-06 21:58 ` Dmitry Gutov
2020-04-06 23:44 ` 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
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=a1ab74ae-8c34-0068-00c6-e3ebdf376b79@yandex.ru \
--to=dgutov@yandex.ru \
--cc=acm@muc.de \
--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).