From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: C-n is very slow in Font-Lock mode
Date: Sat, 23 Apr 2005 23:17:03 +0300 [thread overview]
Message-ID: <01c54841$Blat.v2.4$8f503680@zahav.net.il> (raw)
In-Reply-To: <E1DPNJ5-0007WG-04@fencepost.gnu.org> (message from Richard Stallman on Sat, 23 Apr 2005 12:16:35 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Sat, 23 Apr 2005 12:16:35 -0400
>
> With Font-Lock mode enabled, starting from the beginning of a large
> file (such as fileio.c), C-n with a large argument (I tried C-u 2536
> C-n) took many seconds. I think it was fontifying all the text
> that it moved across.
Probably. JIT lock fontifies any portion of a buffer that is becoming
visible, and C-n makes visible all parts of the buffer it moves
across, one page at a time.
> Can this be avoided? I don't think C-n ought to need to fontify
> all that text.
Try setting jit-lock-defer-time to a non-nil value.
Anyway, C-n is a very inefficient method of paging through a buffer.
If you want to move 2536 lines, you will be better off using goto-line
or C-v. JIT lock is optimized for C-v and similar methods that page
by large chunks of text rather than by one line.
> Even once it has fontified, the command still takes a lot longer
> with Font-Lock mode enabled than it does with Font-Lock disabled.
I'm guessing this is because the display engine looks up all the text
properties put on the text by font-lock.
next prev parent reply other threads:[~2005-04-23 20:17 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 [this message]
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
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='01c54841$Blat.v2.4$8f503680@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).