Font-lock bug in lisp mode

Font-lock bug in lisp mode

[Jesper Harder]

In GNU Emacs 21.2.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-04-09 on porky.devel.redhat.com
configured using `configure  i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop --with-sound'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.iso885915
  locale-coding-system: iso-latin-9
  default-enable-multibyte-characters: t

Font-locking fails in lisp mode when you have a multi-line string with an
opening bracket as the first character of the last line -- subsequent
words are coloured as strings.

Steps to reproduce:

* emacs -q -no-site-file

* Turn on font-lock-mode in a buffer in lisp interaction mode.

* Type:

"foo
("
bar

* "bar" is coloured as a string.

Re: Font-lock bug in lisp mode

[Eli Zaretskii]

On Thu, 5 Sep 2002, Jesper Harder wrote:

> Font-locking fails in lisp mode when you have a multi-line string with an
> opening bracket as the first character of the last line -- subsequent
> words are coloured as strings.

This issue and the way to work around this limitation are documented in 
etc/PROBLEMS.  Search for "Font Lock displays portions of the buffer in 
incorrect faces" in PROBLEMS.

Re: Font-lock bug in lisp mode

[Jesper Harder]

Eli Zaretskii <eliz@is.elta.co.il> writes:

> On Thu, 5 Sep 2002, Jesper Harder wrote:
>
>> Font-locking fails in lisp mode when you have a multi-line string with an
>> opening bracket as the first character of the last line -- subsequent
>> words are coloured as strings.
>
> This issue and the way to work around this limitation are documented in 
> etc/PROBLEMS.

Thanks for the pointer, and sorry about the line noise :-)