From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: acm@muc.de, gregory@heytings.org, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: New optimisations for long raw strings in C++ Mode.
Date: Thu, 11 Aug 2022 19:04:07 +0300 [thread overview]
Message-ID: <83edxmpy14.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8VoVp-=TEM09sqLcZucL0-Fqyt=qfv1zsjzmSQJROTsJg@mail.gmail.com> (message from Yuri Khan on Thu, 11 Aug 2022 22:47:34 +0700)
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Thu, 11 Aug 2022 22:47:34 +0700
> Cc: Eli Zaretskii <eliz@gnu.org>, gregory@heytings.org, larsi@gnus.org, emacs-devel@gnu.org
>
> On Thu, 11 Aug 2022 at 00:36, Alan Mackenzie <acm@muc.de> wrote:
>
> > If you open a file in its middle (e.g., by desktop), and there's an open
> > block comment there, you've got to look arbitrarily far back to detect
> > that state. In practice parse-partial-sexp from point-min will be used,
> > likely with cacheing of whatever sort.
>
> Does fontification need to be synchronous? I.e. you open a file in its
> middle, do you expect it fontified exactly and immediately on first
> render?
>
> Some well-known IDEs[^*] make do with first rendering an inexact
> approximation of syntax highlighting. Then, as the user starts working
> with the buffer, they may have a few thousand idle milliseconds in
> which to improve the approximation.
That's what jit-lock-defer-time is about, I believe (although our
"inexact approximation" is no fontifications at all).
next prev parent reply other threads:[~2022-08-11 16:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 21:29 New optimisations for long raw strings in C++ Mode Alan Mackenzie
2022-08-07 12:49 ` Lars Ingebrigtsen
2022-08-07 13:25 ` Alan Mackenzie
2022-08-07 13:34 ` Lars Ingebrigtsen
2022-08-07 14:40 ` Alan Mackenzie
2022-08-07 14:41 ` Lars Ingebrigtsen
2022-08-07 14:54 ` Lars Ingebrigtsen
2022-08-07 16:13 ` Alan Mackenzie
2022-08-07 16:17 ` Eli Zaretskii
2022-08-09 11:00 ` Alan Mackenzie
2022-08-09 15:35 ` Lars Ingebrigtsen
2022-08-09 15:38 ` Lars Ingebrigtsen
2022-08-09 16:05 ` Alan Mackenzie
2022-08-09 16:34 ` Eli Zaretskii
2022-08-09 20:39 ` Gregory Heytings
2022-08-09 21:43 ` Alan Mackenzie
2022-08-09 23:05 ` Stefan Monnier
2022-08-10 2:43 ` Eli Zaretskii
2022-08-10 7:42 ` Gregory Heytings
2022-08-10 13:28 ` Eli Zaretskii
2022-08-10 16:23 ` Alan Mackenzie
2022-08-10 16:35 ` Eli Zaretskii
2022-08-10 16:50 ` Alan Mackenzie
2022-08-10 16:58 ` Eli Zaretskii
2022-08-10 17:32 ` Alan Mackenzie
2022-08-10 17:41 ` Eli Zaretskii
2022-08-10 22:31 ` Stefan Monnier
2022-08-11 6:21 ` Eli Zaretskii
2022-08-11 7:37 ` Stefan Monnier
2022-08-11 6:27 ` Immanuel Litzroth
2022-08-11 16:54 ` Alan Mackenzie
2022-08-11 17:15 ` Eli Zaretskii
2022-08-12 13:05 ` Lynn Winebarger
2022-08-12 13:18 ` Eli Zaretskii
2022-08-11 15:47 ` Yuri Khan
2022-08-11 16:04 ` Eli Zaretskii [this message]
2022-08-10 17:19 ` Gregory Heytings
2022-08-10 17:21 ` Eli Zaretskii
2022-08-10 19:45 ` Alan Mackenzie
2022-08-14 20:15 ` Alan Mackenzie
2022-08-15 8:00 ` Gregory Heytings
2022-08-10 13:25 ` Eli Zaretskii
2022-08-12 12:44 ` Lars Ingebrigtsen
2022-08-12 12:52 ` Eli Zaretskii
2022-08-07 15:00 ` Eli Zaretskii
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=83edxmpy14.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=yuri.v.khan@gmail.com \
/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).