-- "Triet H. Lai" <thlai(a)mail.usyd.edu.au> spake thusly:
As Norbert reported in the message:
http://list-archive.xemacs.org/xemacs-beta/200104/msg00301.html
font-lock doesn't work well with ruby-mode because it uses a
special form of keyword in `font-lock-syntactic-keywords'
(setq font-lock-syntactic-keywords
'(("\\$\\([#\"'`$\\]\\)" 1 (1 . nil))
("\\(#\\)[{$@]" 1 (1 . nil))
("\\(/\\)\\([^/\n]\\|\\\\/\\)*\\(/\\)"
(1 (7 . ?'))
(3 (7 . ?')))))
`font-lock-apply-highlight' function chokes on the last
keyword:
("\\(/\\)\\([^/\n]\\|\\\\/\\)*\\(/\\)"
(1 (7 . ?'))
(3 (7 . ?')))
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
- open a new file, say ~/tmp/sample.rb
- load ruby-mode and enable it
- start editing ~/tmp/sample.rb: '/test/'
As long as the second forward slash is entered XEmacs popups
an error message:
"(warning/warning) Error caught in `font-lock-pre-idle-hook':
(malformed-list ?\')"
However, if I disable font-lock and then enable it again,
problem goes away for this buffer.
This one looks pretty straightforward. I'll try to find some time this
week to look into it.