[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last steps for pretesting (font-lock-extend-region-function)

From: Alan Mackenzie
Subject: Re: Last steps for pretesting (font-lock-extend-region-function)
Date: Tue, 25 Apr 2006 22:00:00 +0000 (GMT)

Hi, Ralf!

On Tue, 25 Apr 2006, Ralf Angeli wrote:

>* Alan Mackenzie (2006-04-25) writes:

>> On Tue, 25 Apr 2006, Ralf Angeli wrote:

>>>Do you even have to bother with placing font-lock-multiline properties
>>>manually?  In AUCTeX we simply set the font-lock-multiline variable to
>>>t and font-lock added the property automatically.

>> Yes, absolutely!  There are two separate things here which Stefan is
>> failing to distinguish:

>> (i) The matching of keywords which span line breaks;

>> (ii) Extending a font-lock region to include all text needing
>> refontification.

>> If I've understood font-lock-multiline properly, only manually setting
>> f-l-m can achieve purpose (ii).

>As far as I can see font-lock cares about that itself in case of
>keyword fontification if the value of the variable
>`font-lock-multiline' is t.  There are `(put-text-property
>... 'font-lock-multiline t)' calls in
>`font-lock-fontify-achored-keywords' and

Yes, but as far as I can see, these function are capable of putting the
text property only on bytes between BEG and END.  It cannot modify BEG by
applying the property to bytes before BEG.

>As I wrote before, AUCTeX uses this feature without manually adding
>`font-lock-multiline' properties.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]