unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@iwi.uni-sb.de>
Cc: emacs-devel@gnu.org
Subject: Re: Stealth fontification GCs a lot
Date: Fri, 15 Apr 2005 08:47:07 +0200	[thread overview]
Message-ID: <E1DMKbb-0002Vw-Th@neutrino.iwi.uni-sb.de> (raw)
In-Reply-To: <E1DMGpD-0007mZ-Mg@fencepost.gnu.org> (Richard Stallman's message of "Thu, 14 Apr 2005 22:44:55 -0400")

* Richard Stallman (2005-04-15) writes:

>     I don't really mind an initial fontification of the whole buffer.  A
>     worse annoyance of stealth fontification is that this happens again
>     and again after every modification of the buffer.
>
> Are you saying that stealth fontification rechecks the whole buffer
> after any change in it?

I often have that impression.  Now I actually looked at the code and
it does not refontify the whole buffer but the buffer downwards from
the position a change happened.  The doc string of
`jit-lock-after-change' explains that:

(defun jit-lock-after-change (start end old-len)
  "Mark the rest of the buffer as not fontified after a change.
Installed on `after-change-functions'.
START and END are the start and end of the changed text.  OLD-LEN
is the pre-change length.
This function ensures that lines following the change will be refontified
in case the syntax of those lines has changed.  Refontification
will take place when text is fontified stealthily."

-- 
Ralf

  reply	other threads:[~2005-04-15  6:47 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 [this message]
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=E1DMKbb-0002Vw-Th@neutrino.iwi.uni-sb.de \
    --to=angeli@iwi.uni-sb.de \
    --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).