unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Jonathan Yavner <jyavner@member.fsf.org>,
	emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Stealth fontification GCs a lot
Date: Thu, 14 Apr 2005 11:39:37 +0200	[thread overview]
Message-ID: <85br8h4rza.fsf@gnu.org> (raw)
In-Reply-To: <fc339e4a05041323206b17f6c3@mail.gmail.com> (Miles Bader's message of "Thu, 14 Apr 2005 15:20:44 +0900")

Miles Bader <snogglethorpe@gmail.com> writes:

> On 4/14/05, Jonathan Yavner <jyavner@member.fsf.org> wrote:
>> Maybe stealth font-lock is pointless all the time.
>
> Well that's clearly not true.  I think it is pretty hard to tune
> because you'd have to guess what the user's going to do...
>
> 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...),
> which would provide a bit of buffering to make page-movement fast,
> but not spend ages fontifying the entirety of giant source files.

Sounds reasonable.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-04-14  9:39 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 [this message]
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
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=85br8h4rza.fsf@gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jyavner@member.fsf.org \
    --cc=miles@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).