From: "João Távora" <joaotavora@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: jit-lock-antiblink-grace
Date: Mon, 25 Nov 2019 20:23:44 +0000 [thread overview]
Message-ID: <CALDnm50urp+7XyXEhnFgucOpm2Frq9ovGdnKmYZXzU7Lk9Bo3w@mail.gmail.com> (raw)
In-Reply-To: <20191125201115.GD4496@ACM>
On Mon, Nov 25, 2019 at 8:11 PM Alan Mackenzie <acm@muc.de> wrote:
> For me, at least, point 1 doesn't hold. Having the fontification
> delayed until 2 seconds of inactivity would for me be intensely
> irritating.
This is not how it works. The only thing that is delayed is
guaranteed to be unwanted, namely, fontifying as string
a big chunk of the buffer that we know wasn't a string
before the user opened a string.
So what my change does is that this unwanted thing
now comes later, if at all.
> As for point 3, there would be no benefit for me, at least. I want to
> see correct fontification when I type a quote mark, not 2 seconds of
> inactivity later.
Again: this is not how it works. I encourage you to try it out
(and/or read the discussion from the beginning).
And you are confusing two things: One is immediate and
correct fontification, which I agree is desirable, but comes
at a large performance cost for languages that permit multi-line
strings. The other is an improvement on the current situation.
Thanks,
João
next prev parent reply other threads:[~2019-11-25 20:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 22:34 jit-lock-antiblink-grace João Távora
2019-10-11 14:26 ` jit-lock-antiblink-grace Stefan Monnier
2019-10-12 9:34 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 10:57 ` jit-lock-antiblink-grace João Távora
2019-10-12 13:02 ` jit-lock-antiblink-grace Juanma Barranquero
2019-10-12 13:14 ` jit-lock-antiblink-grace João Távora
2019-10-12 14:50 ` jit-lock-antiblink-grace Juanma Barranquero
2019-10-12 15:11 ` jit-lock-antiblink-grace João Távora
2019-10-12 15:30 ` jit-lock-antiblink-grace Juanma Barranquero
2019-10-12 13:32 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 14:13 ` jit-lock-antiblink-grace Stefan Monnier
2019-10-12 14:23 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 14:34 ` jit-lock-antiblink-grace Stefan Monnier
2019-10-12 15:57 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 17:16 ` jit-lock-antiblink-grace Stefan Monnier
2019-10-12 17:50 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 15:47 ` jit-lock-antiblink-grace Alan Mackenzie
2019-10-12 14:23 ` jit-lock-antiblink-grace João Távora
2019-10-12 16:04 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-12 21:55 ` jit-lock-antiblink-grace João Távora
2019-10-13 6:39 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-13 8:47 ` jit-lock-antiblink-grace João Távora
2019-10-13 9:22 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-13 10:28 ` jit-lock-antiblink-grace João Távora
2019-10-13 10:45 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-14 23:29 ` jit-lock-antiblink-grace João Távora
2019-10-15 6:48 ` jit-lock-antiblink-grace Eli Zaretskii
2019-10-15 18:28 ` jit-lock-antiblink-grace João Távora
2019-11-24 1:04 ` jit-lock-antiblink-grace João Távora
2019-11-24 16:16 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-25 18:46 ` jit-lock-antiblink-grace Alan Mackenzie
2019-11-25 19:02 ` jit-lock-antiblink-grace João Távora
2019-11-25 19:26 ` jit-lock-antiblink-grace Alan Mackenzie
2019-11-25 19:45 ` jit-lock-antiblink-grace João Távora
2019-11-25 20:11 ` jit-lock-antiblink-grace Alan Mackenzie
2019-11-25 20:23 ` João Távora [this message]
2019-11-25 21:07 ` jit-lock-antiblink-grace João Távora
2019-11-26 2:30 ` jit-lock-antiblink-grace João Távora
2019-11-26 17:58 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-30 19:11 ` jit-lock-antiblink-grace João Távora
2019-11-30 19:22 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-30 20:12 ` jit-lock-antiblink-grace João Távora
2019-11-30 20:16 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-30 20:19 ` jit-lock-antiblink-grace João Távora
2019-11-30 20:41 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-30 22:00 ` jit-lock-antiblink-grace João Távora
2019-12-01 18:13 ` jit-lock-antiblink-grace Eli Zaretskii
2019-12-04 22:45 ` jit-lock-antiblink-grace João Távora
2019-12-05 15:40 ` jit-lock-antiblink-grace Eli Zaretskii
2019-11-26 13:43 ` jit-lock-antiblink-grace Stefan Monnier
2019-11-25 19:47 ` jit-lock-antiblink-grace Dmitry Gutov
2019-11-25 20:03 ` jit-lock-antiblink-grace João Távora
2019-10-12 16:14 ` jit-lock-antiblink-grace Alan Mackenzie
2019-10-12 22:26 ` jit-lock-antiblink-grace João Távora
2019-10-13 10:18 ` jit-lock-antiblink-grace Alan Mackenzie
2019-10-13 10:48 ` jit-lock-antiblink-grace João Távora
2019-10-13 12:02 ` jit-lock-antiblink-grace Alan Mackenzie
2019-10-13 19:57 ` jit-lock-antiblink-grace João Távora
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=CALDnm50urp+7XyXEhnFgucOpm2Frq9ovGdnKmYZXzU7Lk9Bo3w@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.