Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-23 Thread Stefan Monnier
>> 3. Append a space to the fourth commented line. Bug: fontification of Foo, >> bar, Snafu and snafu is removed from that line. > The problem is that after a textual change, the changed line gets > fontified as an atomic entity, i.e. yanked out of its context. The If you placed a font-lock-mu

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Alan Mackenzie
Hi, Simon; Hi, Richard! On Wed, Jul 19, 2006 at 10:22:00PM -0400, Richard Stallman wrote: > Please DTRT. > --- Start of forwarded message --- > From: "Marshall, Simon" <[EMAIL PROTECTED]> > To: "'Emacs Pretest Bug (emacs-pretest-bug@gnu.org)'" > > Date: Wed, 19 Jul 2006 16:46:04 +0

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Alan Mackenzie
Afternoon, Stefan! On Sun, Jul 23, 2006 at 11:11:45PM -0400, Stefan Monnier wrote: > >> 3. Append a space to the fourth commented line. Bug: > >> fontification of Foo, bar, Snafu and snafu is removed from that > >> line. > > The problem is that after a textual change, the changed line gets > >

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Stefan Monnier
> Put the following in a fubar.cpp: > class Fubar : > public Foo, // Foo fontified as a type, at first > public Bar// Bar fontified as a type, at first > { > Foo bar(Snafu snafu, // Types, function, variable fontified, at first > Foo foo, > Bar bar); > Foo bar(Snafu *snafu, // Types, functi

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Stefan Monnier
>> >> 3. Append a space to the fourth commented line. Bug: >> >> fontification of Foo, bar, Snafu and snafu is removed from that >> >> line. >> > The problem is that after a textual change, the changed line gets >> > fontified as an atomic entity, i.e. yanked out of its context. The >> If you

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Alan Mackenzie
Evening, Stefan! On Mon, Jul 24, 2006 at 10:36:08AM -0400, Stefan Monnier wrote: > >> >> 3. Append a space to the fourth commented line. Bug: > >> >> fontification of Foo, bar, Snafu and snafu is removed from that > >> >> line. > >> > The problem is that after a textual change, the changed line

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Stefan Monnier
> Date: Sun, 30 Apr 2006 12:48:36 + (GMT) > From: Alan Mackenzie <[EMAIL PROTECTED]> > Reply-To: Alan Mackenzie <[EMAIL PROTECTED]> > To: emacs-devel@gnu.org > Subject: font-lock-extend-region-function: Final refinements. > It hasn't as yet been installed, although it would

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Alan Mackenzie
Hi, Stefan! On Mon, Jul 24, 2006 at 04:43:14PM -0400, Stefan Monnier wrote: > > Date: Sun, 30 Apr 2006 12:48:36 + (GMT) > > From: Alan Mackenzie <[EMAIL PROTECTED]> > > Reply-To: Alan Mackenzie <[EMAIL PROTECTED]> > > To: emacs-devel@gnu.org > > Subject: font-lock-extend-re

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-24 Thread Stefan Monnier
>> You haven't shown any evidence of inefficiency. > I think I have, in our previous discussion. I think it's clear that > f-l-multiline properties are erased throughout the change-region, and > have to be recalculated througout the change region, at every change. > For most C-like languages, thi

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-31 Thread Alan Mackenzie
Hi, Stefan! On Mon, Jul 24, 2006 at 10:35:08AM -0400, Stefan Monnier wrote: > The patch below seems to fix number 2 and 3 for me. Someone who > understands cc-fonts.el better than me and thus knows where the two > "public XXX" lines are handled could probably do a similar adjustment > for them.

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-31 Thread Stefan Monnier
>> The patch below seems to fix number 2 and 3 for me. Someone who >> understands cc-fonts.el better than me and thus knows where the two >> "public XXX" lines are handled could probably do a similar adjustment >> for them. > At the very least, this isn't suitable for the CC Mode repository, sinc

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-07-31 Thread Richard Stallman
To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs has nothing to do with GNU. Since XEmacs is a forked version of Emacs, that is a misleading impression. Please write "Emacs" and "XEmacs", or else "GNU Emacs" and "GNU XEmacs". ___

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Romain Francoise
Richard Stallman <[EMAIL PROTECTED]> writes: > To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs > has nothing to do with GNU. Since XEmacs is a forked version of Emacs, > that is a misleading impression. Please write "Emacs" and "XEmacs", > or else "GNU Emacs" and "GNU XEmac

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Alan Mackenzie
Good morning, Richard! On Mon, Jul 31, 2006 at 07:59:55PM -0400, Richard Stallman wrote: > To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs > has nothing to do with GNU. XEmacs isn't maintained by the GNU project. > Since XEmacs is a forked version of Emacs, that is a misle

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Alan Mackenzie
Morning, Stefan! On Mon, Jul 31, 2006 at 06:03:41PM -0400, Stefan Monnier wrote: > >> The patch below seems to fix number 2 and 3 for me. Someone who > >> understands cc-fonts.el better than me and thus knows where the two > >> "public XXX" lines are handled could probably do a similar > >> adjus

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread David Kastrup
Alan Mackenzie <[EMAIL PROTECTED]> writes: > Good morning, Richard! > > On Mon, Jul 31, 2006 at 07:59:55PM -0400, Richard Stallman wrote: > >> To speak of "GNU Emacs" and "XEmacs" gives the impression that >> XEmacs has nothing to do with GNU. > > XEmacs isn't maintained by the GNU project. Corre

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Stefan Monnier
> As a matter of interest, does the f-l-multiline mechanism somehow work > with a _first_ fontification? Assume CC Mode has been enhanced to use > f-l-multiline. Say we have a buffer of C source in fundamental mode (so > there're no f-l-m properties on the buffer), and the top of the screen > is

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Alan Mackenzie
'Evening, Stefan! On Tue, Aug 01, 2006 at 10:55:41AM -0400, Stefan Monnier wrote: > > As a matter of interest, does the f-l-multiline mechanism somehow > > work with a _first_ fontification? Assume CC Mode has been enhanced > > to use f-l-multiline. Say we have a buffer of C source in > > fundam

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Stefan Monnier
> It seems that the identification of the "safe place" (in a previously > unfontified region) needs to be done by a function essentially the same > as font-lock-extend-region-function, since f-l-multiline properties > haven't yet been applied. In that case, what is the advantage in using > f-l-mul

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Richard Stallman
> To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs > has nothing to do with GNU. Since XEmacs is a forked version of Emacs, > that is a misleading impression. Please write "Emacs" and "XEmacs", > or else "GNU Emacs" and "GNU XEmacs". But XEmacs is not a G

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-01 Thread Richard Stallman
"Emacs", unqualified, can be ambiguous. It can mean either (i) "an editor of the Emacs persuasion"; or (ii) "the best editor in the world, maintained by the GNU project". In contexts where it is important to emphasise that (ii) is meant, surely "GNU Emacs" is what to write. Tha

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-02 Thread Aidan Kehoe
Ar an t-aonú lá is triochad de mí Iúil, scríobh Richard Stallman: > To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs has > nothing to do with GNU. Since XEmacs is a forked version of Emacs, that > is a misleading impression. Please write "Emacs" and "XEmacs", or else >

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-02 Thread David Kastrup
Aidan Kehoe <[EMAIL PROTECTED]> writes: > Ar an t-aonú lá is triochad de mí Iúil, scríobh Richard Stallman: > > > To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs has > > nothing to do with GNU. Since XEmacs is a forked version of Emacs, that > > is a misleading impressio

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-02 Thread Aidan Kehoe
Ar an dara lá de mí Lúnasa, scríobh David Kastrup: > And we use the term "Emacs" for referring to Emacs. > When the term "GNU Emacs" is used, it is to draw attention to the GNU > project and the part Emacs plays within it, not to insinuate that the > scope of Emacs is supposed to be restri

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-02 Thread David Kastrup
Aidan Kehoe <[EMAIL PROTECTED]> writes: > Ar an dara lá de mí Lúnasa, scríobh David Kastrup: > > > And we use the term "Emacs" for referring to Emacs. > > > When the term "GNU Emacs" is used, it is to draw attention to the > > GNU project and the part Emacs plays within it, not to insinuate >

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-02 Thread Richard Stallman
For distinguishing the two versions I write "Emacs" and "XEmacs", because the context shows we are talking about these two variants of the original GNU Emacs. In other contexts, there is no need to refer to the two variants but there is a need to connect Emacs with the GNU system. There I write "

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-03 Thread Alan Mackenzie
Morning, Stefan! On Tue, Aug 01, 2006 at 03:23:54PM -0400, Stefan Monnier wrote: > > It seems that the identification of the "safe place" (in a previously > > unfontified region) needs to be done by a function essentially the > > same as font-lock-extend-region-function, since f-l-multiline > > pr

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-03 Thread Alan Mackenzie
Morning, Richard! On Wed, Aug 02, 2006 at 05:20:12PM -0400, Richard Stallman wrote: > For distinguishing the two versions I write "Emacs" and "XEmacs", > because the context shows we are talking about these two variants > of the original GNU Emacs. This leaves a difficulty when there is no contex

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-03 Thread David Kastrup
Alan Mackenzie <[EMAIL PROTECTED]> writes: > Morning, Richard! > > On Wed, Aug 02, 2006 at 05:20:12PM -0400, Richard Stallman wrote: >> For distinguishing the two versions I write "Emacs" and "XEmacs", >> because the context shows we are talking about these two variants >> of the original GNU Emac

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-03 Thread Stefan Monnier
>> > It seems that the identification of the "safe place" (in a previously >> > unfontified region) needs to be done by a function essentially the >> > same as font-lock-extend-region-function, since f-l-multiline >> > properties haven't yet been applied. In that case, what is the >> > advantage i

Re: [EMAIL PROTECTED]: Font Lock on-the-fly misfontification in C++]

2006-08-03 Thread Richard Stallman
I believe "GNU Emacs" is used mainly for unambiguous identification rather than connecting it with the GNU system - much like "John of Gaunt" is used to clarify which John you're talking about rather than to associate him with the town of Gent in Belgium. Yes, exactly. > For d