la 07.06.2005 16:28 Richard Stallman skribis:
Of these five colons only the one before "x" is special. Without
highlighting the multiline string assigned to var "b:c" looks like a
rule, as does the last line. And prior to my rework, the colon in
${var:a=b} was also recognized as a rule separator.
That is a bug, but the behavior of the code I removed was simply
intolerable--a much worse bug.
It's a font-lock bug. Font-lock is documented as being poor on multiline
constructs, irrespective of many file types which desperately need it.
But I don't see where this is much worse! What happens is that
fontification at the point where you are editing can get wrong. Turning
it off and on again repairs it. I much prefer that, to having the file
permanently wrong, as it was in the past.
Maybe we could have a timer based re-font-lock of edited sections?
Here's the original message.
From: Ralf Angeli <[EMAIL PROTECTED]>
To: emacs-pretest-bug@gnu.org
Date: Mon, 30 May 2005 20:08:39 +0200
Subject: [make-mode.el] Multi-line font locking not working correctly
Suppose you want to type the following lines into a new Makefile:
FOO = bar \
bar \
bar
If you type everything by hand from top to bottom, as soon as <TAB> is
typed on the third line, fontification of the second line will
disappear. Content typed in the third line will not be fontified
either.
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
--
lerne / learn / apprends / lär dig / ucz się Esperanto:
http://lernu.net/
_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug