Hi, Mats!
On Sat, Aug 2, 2014 at 7:01 PM, Mats Lidell <matsl(a)xemacs.org> wrote:
Looking at some old bug reports on XEmacs in Gentoo I found this
problem that is still present in 21.4.22.
The recipe is:
$ xemacs -q
> M-x font-lock-mode RET
> Paste this text below to the *scratch* buffer and evaluate it
(font-lock-add-keywords nil
'(("\\<\\(FIXME\\):" 1 font-lock-warning-face prepend)
("\\<\\(and\\|or\\|not\\)\\>" . font-lock-keyword-face)))
This results in the error message:
(1) (warning/warning) Error caught in `font-lock-pre-idle-hook':
(invalid-function 1)
This problem was in Gentoo reported also for 21.5.28. It seems though
that is has been fixed because with 21.5.34 I'm not able to reproduce.
Is this a known problem? Is it known to have been fixed for 21.5?
Would it possible to fix for 21.4 as well?
I get the same results from 21.4 (latest hg sources) as I do from 21.5;
here's the lossage:
Recent keystrokes:
button1 button1up M-x f o n t - l o c k - m o d e RET
button2 button2up C-x C-e C-h L
Recent minibuffer messages (most recent first):
(t ("\\<\\(FIXME\\):" (1 font-lock-warning-face prepend))
("\\<\\(and\\|or\\|not\\)\\>" (0 font-lock-keyword-face))
("^(\\(def\\(\\(const\\(\\|ant\\)\\|ine-key\\(\\|-after\\)\\|var\\|custom\\)\\|\\(class\\|struct\\|type\\)\\|\\([^
()]+\\)\\)\\)\\>[ '(]*\\([^
()]+\\)?" (0 font-lock-keyword-face)) (1 (font-lock-keyword-face)) (8 (cond
((match-beginning 3) (quote font-lock-variable-name-face))
((match-beginning 6) (quote font-lock-type-face)) (t (quote
font-lock-function-name-face))) nil t))
Fontifying *scratch*... done.
Loading font-lock...done
Fontifying *scratch*... (syntactically).
Fontifying *scratch*...
Loading cus-face...done
Loading cus-face...
Loading font-lock...
I could generate a new 21.4 release if there were sufficient demand.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta