[debbugs-tracker] bug#15270: closed (24.3; ruby-mode font-lock bug related to HERE docs)

[GNU bug Tracking System]

Your message dated Thu, 05 Sep 2013 16:06:21 +0300
with message-id <address@hidden>
and subject line Re: bug#15270: 24.3; ruby-mode font-lock bug related to HERE 
docs
has caused the debbugs.gnu.org bug report #15270,
regarding 24.3; ruby-mode font-lock bug related to HERE docs
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
15270: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15270
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: 24.3; ruby-mode font-lock bug related to HERE docs Date: Thu, 5 Sep 2013 11:39:03 +0300

Code like the following breaks font-locking logic of ruby-mode:

expected_source = <<-END.strip_indent

              each do |x|

                some_method

                other_method

              end

            END

The second END gets highlighted as a constant, instead of a string. I guess the two consecutive ends cause the problem.

Here's a screenshot - http://i42.tinypic.com/122jeap.jpg

In GNU Emacs 24.3.1 (x86_64-apple-darwin12.4.0, NS apple-appkit-1187.39)

 of 2013-08-12 on Bozhidars-MacBook-Pro.local

Windowing system distributor `Apple', version 10.3.1187

Configured using:

 `configure '--prefix=/usr/local/Cellar/emacs/24.3' '--without-dbus'

 '--enable-locallisppath=/usr/local/share/emacs/site-lisp'

 '--infodir=/usr/local/Cellar/emacs/24.3/share/info/emacs'

 '--without-gnutls' '--with-ns' '--disable-ns-self-contained' 'CC=cc''

-- 

Cheers,

Bozhidar

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#15270: 24.3; ruby-mode font-lock bug related to HERE docs
>
>
>
>
> Date: 
>
> Thu, 05 Sep 2013 16:06:21 +0300
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
>
>
>
>
> Version: 24.4
>
> On 05.09.2013 14:48, Bozhidar Batsov wrote:
> > I guess this is fixed in the trunk, but I think the highlighting of the
> > first END in the heredoc should be corrected as well.
>
> Ok, fixed for heredocs (gave BEGIN/END lower priority).
>
>
> --- End Message ---