unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: jit-lock doesn't honor font-lock-lines-before
Date: Tue, 30 Aug 2005 08:54:13 +0200	[thread overview]
Message-ID: <43140295.4000102@gmx.at> (raw)
In-Reply-To: <E1E9fAo-0005BX-Ax@fencepost.gnu.org>

 >     (2) Modify `jit-lock-after-change' appropriately by, for example, inserting
 >
 > 	    (forward-line (- font-lock-lines-before))
 >
 > 	 before
 >
 > 	    (setq start (line-beginning-position))
 >
 > That seems like the right fix.  Why do you think it isn't?
 >
 >

Because this means that every time I insert one character, redisplay
would refontify `font-lock-lines-before' in addition to the current
line.  I suppose that the impact of this variable has not been noticed
so far because jit-lock doesn't consider it.

On the other hand, jit-lock wouldn't be able to handle this variable in
the same way as font-lock does: font-lock refontifies immediately in the
after-change hook.  jit-lock's after-change hook would only reset the
fontified property to nil.  Whether and when these lines are refontified
would be _also_ decided by the redisplay engine.  And the latter doesn't
know about `font-lock-lines-before'.  For example, editing the first
line in a window would not "include the line before in refontification".

  reply	other threads:[~2005-08-30  6:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 13:08 jit-lock doesn't honor font-lock-lines-before martin rudalics
2005-08-29  8:39 ` Richard M. Stallman
2005-08-30  6:54   ` martin rudalics [this message]
2005-08-31  0:23     ` Richard M. Stallman
2005-09-01  6:22       ` martin rudalics
2005-09-01 14:11         ` Stefan Monnier
2005-09-02  5:24           ` martin rudalics
2005-09-02  6:04         ` Richard M. Stallman
2005-09-02 14:30           ` Stefan Monnier
2005-08-31 14:36     ` Richard M. Stallman
2005-08-29 14:13 ` Stefan Monnier
2005-08-30 12:11   ` martin rudalics
2005-08-31  2:47     ` Stefan Monnier
2005-09-01  6:24       ` martin rudalics
2005-09-01 13:49         ` Stefan Monnier
2005-09-02  6:05           ` Richard M. Stallman
2005-09-02 18:45             ` Stefan Monnier
2005-09-03  9:07               ` Richard M. 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=43140295.4000102@gmx.at \
    --to=rudalics@gmx.at \
    --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).