Stefan Monnier <[EMAIL PROTECTED]> writes:
>> signal(error ("Font-lock trying to use keywords before setting them up"))
>> error("Font-lock trying to use keywords before setting them up")
>> font-lock-compile-keywords(nil t)
>> font-lock-fontify-keywords-region(1 81 nil)
>> font-lock-default-fontify-region(1 80 nil)
>> font-lock-fontify-region(1 80)
>> mh-add-sequence-notation(1 t)
>
> So it looks like the problem is that you call font-lock-fontify-region
> without first setting up font-lock variables (e.g. by calling
> font-lock-mode or font-lock-set-defaults).
The manual doesn't mention either font-lock-fontify-buffer or
font-lock-fontify-region. Is that because the manual is incomplete or
because we are using font-lock in an undocumented way?
Nonetheless, if font-lock-default-fontify-buffer calls
font-lock-set-defaults, it seems that font-lock-default-fontify-region
should as well, thereby fixing the problem.
--
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
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
