Ruby-mode font-lock trouble on Gnu Emacs 21.3.1

I’ve been using ruby-mode along with a number of different Emacsen over the
past year. When I was using Xemacs, I experienced all of the well-known
problems with font-locking then. But, when I migrated over to Gnu Emacs
21.3.1, those went away, and font-locking worked fine. It looked beautiful. A
little later on, and this baffled me, Gnu Emacs started doing the same thing
Xemacs did.

  • Only comments and strings are font-locked
  • If I use “#{}” as the parameter to a function, it messes up the indenting.

There were a few other things as well. I haven’t yet tried the fix that I saw
posted for Xemacs. What baffles me is that I didn’t make any changes to my
Emacs installation to cause it to suddenly stop working.

Any ideas?

Thanks,
Samuel

Samuel Tesla samuel@alieniloquent.com writes:

There were a few other things as well. I haven’t yet tried the fix that I
saw posted for Xemacs. What baffles me is that I didn’t make any changes to
my Emacs installation to cause it to suddenly stop working.

Upon closer inspection, the fix I saw was for a really old version of
ruby-mode.el, and doesn’t seem to apply to the latest version that ships with
1.8.0.

Hi,

···

In message “Re: ruby-mode font-lock trouble on Gnu Emacs 21.3.1” on 03/12/27, Samuel Tesla samuel@thoughtlocker.net writes:

Upon closer inspection, the fix I saw was for a really old version of
ruby-mode.el, and doesn’t seem to apply to the latest version that ships with
1.8.0.

Perhaps we forgot to apply the fix. Where did you find the patch?

						matz.

matz@ruby-lang.org (Yukihiro Matsumoto) writes:

Perhaps we forgot to apply the fix. Where did you find the patch?

I doubt that’s the case. This was from back in 2001. It was on the ruby-talk
list. The changelogs indicate that they were incorporated a long time ago.

Like I said in the OP, the weirdest thing was when I switched from Xemacs to
Gnu Emacs, it worked. Then a couple of days later it suddenly didn’t (and no
changes were made…just closed and reopened emacs). Hasn’t worked since.

– Samuel

I have also seen the problem with using #{} messing things up. The ‘fix’
for me is just to add a # at the end of the line with the #{} on it and
the indenting works fine afterwards. It doesn’t always happen, which is
strange, but I guess it depends on what has come before and what Emacs
things is happening.

Joey

···

On 12/26/2003 7:56 PM, Samuel Tesla wrote:

Like I said in the OP, the weirdest thing was when I switched from Xemacs to
Gnu Emacs, it worked. Then a couple of days later it suddenly didn’t (and no
changes were made…just closed and reopened emacs). Hasn’t worked since.


Never trust a girl with your mother’s cow
never let your trousers go falling down in the green grass…

http://www.joeygibson.com/blog

Joey Gibson joey@joeygibson.com writes:

I have also seen the problem with using #{} messing things up. The ‘fix’
for me is just to add a # at the end of the line with the #{} on it and
the indenting works fine afterwards. It doesn’t always happen, which is
strange, but I guess it depends on what has come before and what Emacs
things is happening.

Yeah, I’ve done similar things. I also, sometimes, simply assign the string to
a variable, and then pass the variable.

Alas, when Emacs governs my coding style… :stuck_out_tongue:

It’s the syntax hilighting that really bugs me, though.

– Samuel