Error message in Makefile mode when font-lock-mode is active.

Error message in Makefile mode when font-lock-mode is active.

[Jens Kilian]

In GNU Emacs 21.3.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2003-05-22 on porky.devel.redhat.com

configured using `configure --host=i386-redhat-linux
--build=i386-redhat-linux --target=i386-redhat-linux-gnu
--program-prefix= --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: C
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

I have the following settings for font-lock-mode in my ~/.emacs file:

       (setq font-lock-support-mode 'lazy-lock-mode)
       (setq font-lock-maximum-decoration t)
       (global-font-lock-mode t)

When I load a Makefile containing an "include" statement, like the following:
---8<-------------------------------------------------------------------8<---
include foo
---8<-------------------------------------------------------------------8<---

I get the error message:

(error No match 2 in highlight (2 font-lock-variable-name-face))


Regards,

	Jens.
-- 
mailto:jjk@acm.org                 phone:+49-7031-464-7698 (TELNET 778-7698)
  http://www.bawue.de/~jjk/          fax:+49-7031-464-7351
                                   As the air to a bird, or the sea to a fish,
                                   so is contempt to the contemptible. [Blake]

Re: Error message in Makefile mode when font-lock-mode is active.

[Kevin Rodgers]

Jens Kilian wrote:
 > In GNU Emacs 21.3.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
 >  of 2003-05-22 on porky.devel.redhat.com
...
 > I have the following settings for font-lock-mode in my ~/.emacs file:
 >
 >        (setq font-lock-support-mode 'lazy-lock-mode)
 >        (setq font-lock-maximum-decoration t)
 >        (global-font-lock-mode t)
 >
 > When I load a Makefile containing an "include" statement, like the following:
 > ---8<-------------------------------------------------------------------8<---
 > include foo
 > ---8<-------------------------------------------------------------------8<---
 >
 > I get the error message:
 >
 > (error No match 2 in highlight (2 font-lock-variable-name-face))

I can't replicate that here: GNU Emacs 21.3.1 (i386-pc-solaris2.7, X
toolkit) of 2003-04-24 on briard.

Does it happen if you start emacs with -q --no-site-file, and evaluate
those forms in the *scratch* buffer?

-- 
Kevin Rodgers

Re: Error message in Makefile mode when font-lock-mode is active.

[Jens Kilian]

Kevin Rodgers <ihs_4664@yahoo.com> writes:
> Jens Kilian wrote:
>  > In GNU Emacs 21.3.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
>  >  of 2003-05-22 on porky.devel.redhat.com
> ...
>  > I have the following settings for font-lock-mode in my ~/.emacs file:
>  >
>  >        (setq font-lock-support-mode 'lazy-lock-mode)
>  >        (setq font-lock-maximum-decoration t)
>  >        (global-font-lock-mode t)
>  >
>  > When I load a Makefile containing an "include" statement, like the following:
>  > ---8<-------------------------------------------------------------------8<---
>  > include foo
>  > ---8<-------------------------------------------------------------------8<---
>  >
>  > I get the error message:
>  >
>  > (error No match 2 in highlight (2 font-lock-variable-name-face))
> 
> I can't replicate that here: GNU Emacs 21.3.1 (i386-pc-solaris2.7, X
> toolkit) of 2003-04-24 on briard.
> 
> Does it happen if you start emacs with -q --no-site-file, and evaluate
> those forms in the *scratch* buffer?

Yes.  The culprit seems to be the lazy-lock-mode, if I use jit-lock-mode
the problem goes away.  (I.e., I have a workaround now :-)

Bye,
        Jens.
-- 
mailto:jjk@acm.org                 phone:+49-7031-464-7698 (TELNET 778-7698)
  http://www.bawue.de/~jjk/          fax:+49-7031-464-7351
                                   As the air to a bird, or the sea to a fish,
                                   so is contempt to the contemptible. [Blake]