From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Stealth fontification GCs a lot
Date: Thu, 14 Apr 2005 15:04:00 -0400 [thread overview]
Message-ID: <E1DM9dA-0007XV-8k@fencepost.gnu.org> (raw)
In-Reply-To: <200504140017.50453.jyavner@member.fsf.org> (message from Jonathan Yavner on Thu, 14 Apr 2005 00:17:50 -0400)
I love JIT font-lock and depend on it for proper operation of HAPE, but
stealth-fontification is pointless when working on a 2MB file that's heavily
fontified but probably much less than 1% of it will be looked at during any
one editing session.
Perhaps stealth fontification should be turned off for files larger
than a certain size.
Or perhaps with Eli's revised parameters it is so harmless that you
may as well have it enabled for these files too. After all, suppose
you visit the file and then spend half an hour on the phone. It could
have fontified the whole thing for you in that much time--so why
not do so?
Maybe it should only try to stealth-fontify some amount of text before
and after the current point (e.g., 100 lines before and after; if the
user moves, then just give up on the old position...),
That might be a good idea, but 100 lines is clearly too little.
500 or 1000 might be better.
next prev parent reply other threads:[~2005-04-14 19:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DLrVe-00055D-2l@monty-python.gnu.org>
2005-04-14 4:17 ` Stealth fontification GCs a lot Jonathan Yavner
2005-04-14 6:20 ` Miles Bader
2005-04-14 9:39 ` David Kastrup
2005-04-14 11:25 ` Ralf Angeli
2005-04-15 2:44 ` Richard Stallman
2005-04-15 6:47 ` Ralf Angeli
2005-04-16 2:57 ` Richard Stallman
2005-04-15 8:27 ` Eli Zaretskii
2005-04-15 9:12 ` Ralf Angeli
2005-04-14 19:04 ` Richard Stallman [this message]
2005-04-15 8:50 ` Eli Zaretskii
2005-04-11 1:57 Richard Stallman
2005-04-11 3:40 ` Stefan Monnier
2005-04-11 22:22 ` Eli Zaretskii
2005-04-12 17:25 ` Richard Stallman
2005-04-12 18:55 ` Eli Zaretskii
2005-04-12 19:52 ` Stefan Monnier
2005-04-13 17:29 ` Eli Zaretskii
2005-04-13 17:56 ` Stefan Monnier
2005-04-13 23:41 ` Miles Bader
2005-04-14 16:21 ` Richard Stallman
2005-04-13 18:30 ` Richard Stallman
2005-04-13 21:24 ` Aidan Kehoe
2005-04-13 22:25 ` Stefan Monnier
2005-04-14 3:59 ` Eli Zaretskii
2005-04-14 19:03 ` Richard Stallman
2005-04-15 8:34 ` Eli Zaretskii
2005-04-13 18:31 ` Richard Stallman
2005-04-14 3:57 ` Eli Zaretskii
2005-04-14 19:03 ` Richard Stallman
2005-04-23 12:49 ` Eli Zaretskii
2005-04-12 2:59 ` Richard Stallman
2005-04-12 8:29 ` Ralf Angeli
2005-04-13 5:02 ` Richard Stallman
2005-04-13 11:37 ` Ralf Angeli
2005-04-14 16:20 ` Richard Stallman
2005-04-14 16:53 ` Ralf Angeli
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=E1DM9dA-0007XV-8k@fencepost.gnu.org \
--to=rms@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).