Re: font-lock bug in fundamental mode

Re: font-lock bug in fundamental mode

[Richard M. Stallman]

    With emacs 22.0.50.1 under Mac OS X 10.4.2 (installed via darwinports),
    I have the following problem. Consider the following emacs-test file:

    (add-to-list 'load-path "/opt/local/share/emacs/site-lisp")
    (require 'font-lock)
    (global-font-lock-mode t)
    (setq font-lock-maximum-decoration t)
    (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)

    I open it with:

      emacs -no-site-file -q -l emacs-test emacs-test
    At this time, nothing has been colorized yet (this is OK). But
    if I add something like a blank line at the beginning of the
    file ([Enter] key), then the string

      "/opt/local/share/emacs/site-lisp"

    gets colorized. This shouldn't happen in fundamental mode.

I cannot reproduce it on GNU/Linux.

Re: font-lock bug in fundamental mode

[Vincent Lefevre]

I reported the following bug a few months ago...

On 2005-09-01 11:52:35 -0400, Richard M. Stallman wrote:
>     With emacs 22.0.50.1 under Mac OS X 10.4.2 (installed via darwinports),
>     I have the following problem. Consider the following emacs-test file:
> 
>     (add-to-list 'load-path "/opt/local/share/emacs/site-lisp")
>     (require 'font-lock)
>     (global-font-lock-mode t)
>     (setq font-lock-maximum-decoration t)
>     (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
> 
>     I open it with:
> 
>       emacs -no-site-file -q -l emacs-test emacs-test
>     At this time, nothing has been colorized yet (this is OK). But
>     if I add something like a blank line at the beginning of the
>     file ([Enter] key), then the string
> 
>       "/opt/local/share/emacs/site-lisp"
> 
>     gets colorized. This shouldn't happen in fundamental mode.

[I recall this was under Mac OS X.]

> I cannot reproduce it on GNU/Linux.

Now I could test it by myself under Linux... I've just installed the
emacs-snapshot-gtk Debian package:

emacs-snapshot-bin-common       20051124-1
emacs-snapshot-common           20051124-1
emacs-snapshot-el               20051124-1
emacs-snapshot-gtk              20051124-1

and I have exactly the same problem.

ay:~> emacs --version
GNU Emacs 22.0.50.1
[...]

The messages:
------------------------------------------------------------------
(emacs -q -no-site-file -l emacs-test emacs-test)
Loading disp-table...done
For information about the GNU Project and its goals, type C-h C-p.
Loading lazy-lock...done
Package lazy-lock is obsolete
------------------------------------------------------------------

Could it be due to the fact that Package lazy-lock is obsolete?
Unfortunately, it doesn't say what to use instead.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: font-lock bug in fundamental mode

[Richard M. Stallman]

    Now I could test it by myself under Linux...

Don't you mean "under GNU/Linux"?

Meanwhile, I am not sure I understand this:

    I've just installed the
    emacs-snapshot-gtk Debian package:

but I think it means you're not using the latest development Emacs
sources.  In that case, it is not entirely clear what conclusion to
draw.  Maybe you are seeing a bug that has been fixed.

Can you make it fail with the latest Emacs sources?

Re: font-lock bug in fundamental mode

[Vincent Lefevre]

On 2005-11-27 17:34:27 -0500, Richard M. Stallman wrote:
>     Now I could test it by myself under Linux...
> 
> Don't you mean "under GNU/Linux"?

Oops, sorry, yes.

> Meanwhile, I am not sure I understand this:
> 
>     I've just installed the
>     emacs-snapshot-gtk Debian package:
> 
> but I think it means you're not using the latest development Emacs
> sources.  In that case, it is not entirely clear what conclusion to
> draw.  Maybe you are seeing a bug that has been fixed.

I've had a mail by the package maintainer, telling me that lazy-lock
is "hopelessly buggy", and suggested not to use it (jit-lock used by
default being sufficient). This is OK for me.

In fact, I had lazy-lock selected in my .emacs for years; I didn't
know that things have been improved and that it is now useless.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA