From: nobu.nokada@...
Date: 2001-12-31T05:01:08+09:00
Subject: [ruby-talk:29757] Re: ruby-mode and xemacs

At Mon, 31 Dec 2001 04:20:40 +0900,
Vincent Bernat <bernat@scientist.com> wrote:
> >> I use XEmacs 21.4.6 "Common Lisp" and I have run through the same
> >> problem with XEmacs 21.4.4 "Artificial Intelligence". I have tried
> >> ruby-mode revision 1.37 (the latest one) and ruby-mode from Ruby 1.6.5
> >> with no changes. I have loaded font-lock prior to the ruby-mode with
> >> no changes.
> 
> > The latest ruby-mode.el is 1.39.
> 
> I have the same problem with this one.

Possibly, is it same as the second issue in [ruby-talk:29296]?
Then patches in [ruby-talk:29370], [ruby-talk:29527] and
[ruby-talk:29558] may help you.

At Sat, 22 Dec 2001 15:55:11 +0900,
Le Wang <> wrote:
> or this baby when I have lazy-shot enabled:
> -------------------------------------
> Signaling: (invalid-function 1)
>   (1)
>   eval((1))
>   font-lock-fontify-keywords-region(1 1056 nil)
>   font-lock-default-fontify-region(1 1056 nil)
>   font-lock-fontify-region(1 1056)
>   lazy-shot-fontify-internal(#<buffer "jam"> 1 1038 t "")
>   lazy-shot-lock-extent(#<destroyed extent> nil)
>   lazy-shot-redisplay-function(#<destroyed extent>)
> -------------------------------------

-- 
Nobu Nakada