The second = in this code causes ruby-mode to mark everything after it as a string.
T = <<EOQ
Steve
The second = in this code causes ruby-mode to mark everything after it as a string.
T = <<EOQ
<%= @text %> EOQSteve
<%= @text %> EOQ >cat c.rb
puts <<EOQ
<%= @text %> >ruby c.rb
Looking in Rubys ref-manual… it seems normal to me.
http://www.ruby-lang.org/en/man-1.4/syntax.html#here_doc
Is there a problem with it ?
···
On Wed, 14 May 2003 10:16:39 +0000, Steven Lumos wrote:
–
Simon Strandgaard
“Simon Strandgaard” 0bz63fz3m1qt3001@sneakemail.com writes:
···
On Wed, 14 May 2003 10:16:39 +0000, Steven Lumos wrote:
The second = in this code causes ruby-mode to mark everything after it as a string.
T = <<EOQ
<%= @text %> EOQSteve
<%= @text %> EOQ >cat c.rb
puts <<EOQ<%= @text %> >ruby c.rb
Looking in Rubys ref-manual… it seems normal to me.
http://www.ruby-lang.org/en/man-1.4/syntax.html#here_docIs there a problem with it ?
Sorry. I wasn’t very clear.
I’m talking about Emacs ruby-mode font-locking (highlighting,
colorizing, whatever). With the above at the top of a source file,
everything in the file after the second = will have the color for
string instead of the correct color.
Steve
> I'm talking about Emacs ruby-mode font-locking (highlighting,
> colorizing, whatever). With the above at the top of a source file,
> everything in the file after the second = will have the color for
> string instead of the correct color.
Yeah, there are other problems, too. For instance, <<HERE blocks
are not counted as quotes, which is both slightly annoying and
problematic for indentation. Anyone out there want to hack on
ruby-mode? 
···
On Thu, 15 May 2003 02:45:07 +0900 slumos@yahoo.com wrote:
–
Ryan Pavlik rpav@users.sf.net
“Alas Quantum Mechanics Plan ALPHA, the day was not ours.” - 8BT