From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: C-n is very slow in Font-Lock mode
Date: Wed, 27 Apr 2005 12:19:27 +0300 [thread overview]
Message-ID: <01c54b0a$Blat.v2.4$5b6307a0@zahav.net.il> (raw)
In-Reply-To: <85hdhtf8ou.fsf@lola.goethe.zz> (message from David Kastrup on Wed, 27 Apr 2005 00:57:05 +0200)
> Cc: emacs-devel@gnu.org
> From: David Kastrup <dak@gnu.org>
> Date: Wed, 27 Apr 2005 00:57:05 +0200
>
> Without looking at the code, it would be my guess that it would
> currently run immediately after redisplay, whereas my suggestion for
> jit-lock-defer-time=0 semantics would be that it be run immediately
> before redisplay.
I'm not sure what that means. You _are_ aware that, when you scroll
thru text with C-n or C-v, there's almost nothing going on in Emacs
_except_ redisplay, yes? That is, all C-n does is move point one
line; the rest is redisplay's job, including fontification. (The
single most important new aspect of JIT lock as opposed to the old
lazy-lock and its ilk was that JIT lock uses special hooks of the
display engine, whereas the old, pre-v21 redisplay didn't have such
hooks, and so lazy-lock needed to jump through the hoops to hook into
every possible method of changing the displayed text.)
So when you are saying ``before redisplay'', what exactly do you mean?
Redisplay begins by computing the ``desired glyph matrix'', which is
an internal representation of what should be on the screen; surely,
before this happens, there's no way we could fontify the right portion
of the text, since we have no idea what that portion is.
> > And fontification of the visible portion will take time during which
> > one still sees unfontified text, anyway.
>
> Not if it happens before redisplay. [...]
>
> It would possibly make sense to implement this distinction in the
> context of run-with-idle-timer, and then let jit-lock-defer-time just
> use it by defaulting to -1.
Idle timers run when Emacs is idle, which by definition is _after_
redisplay did its job. So I think you are talking about some nw
mechanism, which has nothing to do with how jit-lock-defer-time works
now.
> Again: I have not looked at the code.
Well, perhaps you should.
next prev parent reply other threads:[~2005-04-27 9:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 16:16 C-n is very slow in Font-Lock mode Richard Stallman
2005-04-23 20:17 ` Eli Zaretskii
2005-04-24 21:23 ` Richard Stallman
2005-04-24 21:50 ` Eli Zaretskii
2005-04-26 10:05 ` Richard Stallman
2005-04-26 10:27 ` David Kastrup
2005-04-26 22:56 ` Richard Stallman
2005-04-27 8:59 ` Kim F. Storm
2005-04-27 9:57 ` Eli Zaretskii
2005-04-27 12:27 ` Kim F. Storm
2005-04-27 9:06 ` Eli Zaretskii
2005-04-28 11:00 ` Richard Stallman
2005-04-26 18:05 ` Eli Zaretskii
2005-04-26 21:38 ` David Kastrup
2005-04-26 22:43 ` Eli Zaretskii
2005-04-26 22:57 ` David Kastrup
2005-04-27 9:19 ` Eli Zaretskii [this message]
2005-04-27 9:43 ` David Kastrup
2005-04-27 10:17 ` Eli Zaretskii
2005-04-27 11:32 ` David Kastrup
2005-04-27 11:59 ` Eli Zaretskii
2005-04-27 12:23 ` David Kastrup
2005-04-27 12:32 ` Kim F. Storm
2005-04-28 11:00 ` Richard Stallman
2005-04-28 12:16 ` David Kastrup
2005-04-28 11:00 ` Richard Stallman
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='01c54b0a$Blat.v2.4$5b6307a0@zahav.net.il' \
--to=eliz@gnu.org \
--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).