From: kamphausen@... (SKa)
Date: 2001-10-29T19:40:51+09:00
Subject: [ruby-talk:23714] Re: ruby-mode.el: error in font-locking

Hi,

sorry for the delay - I'm following the group via google only.


matz@ruby-lang.org (Yukihiro Matsumoto) wrote in message news:<1003733542.336910.19762.nullmailer@ev.netlab.jp>...
> Hi,
> 
> In message "[ruby-talk:22743] ruby-mode.el: error in font-locking"
>     on 01/10/19, SKa <kamphausen@novelscience.com> writes:
> 
> |once again I think I found a (minor) flaw in ruby-mode.el. Though the
> |font locking (aka syntax highlighting) has improved a lot (in revision
> |1.34 and 1.35 compared to 1.2x) it still gets confused from time to
> |time.
> 
> Your example works fine on my box (Linux, Emacs 20.7.2, ruby-mode 1.35).
> Could you supply me additional information?

what else would you need? If I typed exactly what is written above in
XEmacs, 21.1.8 using ruby-mode 1.34 (into which I put the patch to
1.35 by hand) I get the wrong highlighting.

OK, I just checked to make sure and I found that if the line
@instance_var.each do has a space somewhere in the leading whitespaces
it works. When there is only one TAB it doesn't highlight correctly.
Same for example two: just error when only one TAB at the beginning of
the line.
This makes no difference in the third case, anyway.

I hope this helps more.
Respect
stefan kamphausen