Juri Linkov <[EMAIL PROTECTED]> writes:
>> font-lock-keywords in the affected Gnus buffers is (t nil).
>>
>> [...]
>>
>> Is that enough information to find the culprit, or is there a watch I
>> can put on the global value of font-lock-keywords which will print a
>> stacktrace or enter the debugger when it is changed?
> ...
>
> Before fixing it, it would be useful to know how it gets called.
> In the buffer list you sent earlier there is the *Occur* buffer.
> Do you remember on what buffer you called `occur'? Very likely
> `occur' forced fontification on a non-font-lock buffer.
It's most likely to have been one of these two:
* mh-e.texi 309787 Texinfo
/usr/local/src/mh-e/doc/mh-e.texi
mh-customize.el 111626 Emacs-Lisp
/usr/local/src/mh-e/src/emacs/lisp/mh-e/mh-customize.el
As you can imagine, both have extensive font-lock-keywords settings; I
do have this in my custom-set-variables so font-lock is turned on.
'(global-font-lock-mode t nil (font-lock))
I suppose it is no longer needed except for Emacs 21 compatibility.
> However, I can't reproduce this bug with `emacs -Q'. Do you have a
> special font-lock configuration in .emacs, like calling
> `(font-lock-turn-on-thing-lock)' directly on non-font-lock buffers
> or something like that?
Nope, that setting above is the only hit for "font" in my loaded
modules.
Would it help to check the value of font-lock-keywords before and
after running list-matching-lines?
--
Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
