GNU bug report logs - #8626
24.0.50; (elisp) Region to Fontify after a Buffer Change - Why a child of Multiline Font Lock?

Previous Next

Package: emacs;

Reported by: "Drew Adams" <drew.adams <at> oracle.com>

Date: Thu, 5 May 2011 22:22:02 UTC

Severity: minor

Tags: notabug

Found in version 24.0.50

Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #30 received at 8626 <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi <at> gnus.org>,
	"'Stefan Monnier'" <monnier <at> iro.umontreal.ca>
Cc: 8626 <at> debbugs.gnu.org
Subject: RE: bug#8626: 24.0.50;
	(elisp) Region to Fontify after a Buffer Change - Why a child of
	Multiline Font Lock?
Date: Fri, 15 Jul 2011 07:30:35 -0700
If you dropped into this node from elsewhere than it parent, you would see
nothing about multiline font-lock constucts.  (And even coming from that node
you will see nothing about them.)

You would learn about refontifying the region after a buffer change, in
particular that in some cases refontifying needs to extend the region.  That's
all.

No one has yet answered the question that would unambiguously tie this to
multiline font-lock constructs: is this region extension for refontifying
pertinent _ONLY_ in the context of multi-line font-lock constructs?  As I said:

> If the _only_ time this is pertinent is in the context of 
> multiline font-lock constructs, then please say so (and
> perhaps why, if helpful).  If it is not the only time, then
> add that this _can_ happen, in particular, in 
> the context of multiline font-lock constructs.

Answer that question for readers and you've fixed this bug.





This bug report was last modified 14 years and 8 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.