From: Le Wang <>
Date: 2001-12-22T15:55:11+09:00
Subject: [ruby-talk:29296] XEmacs problems with ruby-mode.el

Hi,

Anyone know what the story is with the XEmacs and ruby-mode.el?  I
always get really weird errors, and when I have font-lock enabled and
scroll thru a ruby file.  Here is a sample:

-------------------------------------
Signaling: (beginning-of-buffer)
  signal(beginning-of-buffer nil)
  scroll-signal-boundary-error(1 -30)
  scroll-window-in-place(#<window on "jam" 0x2102> nil -1)
  scroll-window(#<window on "jam" 0x2102> nil -1)
  scroll-down(nil)
  scroll-down-command(nil)
  call-interactively(scroll-down-command)
-------------------------------------



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>)
-------------------------------------


Matz keeps updating ruby-mode.el, (up to 1.39 now, I think).  But this
problem is just not going away...


-lw