[debbugs-tracker] bug#30075: closed (etags misdetects ruby sharp-bang sequence)

[GNU bug Tracking System]

Your message dated Fri, 12 Jan 2018 01:50:41 +0300
with message-id <address@hidden>
and subject line Re: bug#30075: etags misdetects ruby sharp-bang sequence
has caused the debbugs.gnu.org bug report #30075,
regarding etags misdetects ruby sharp-bang sequence
to be marked as done.

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


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

--- Begin Message --- Subject: etags misdetects ruby sharp-bang sequence Date: Thu, 11 Jan 2018 02:36:55 +0300 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Thunderbird/58.0 Here's a file that is parsed wrongly when it has no .rb extension. The sharp-bang sequence at the top looks correct to me.

Attaching both the input file and the generated tags file.

The problem is present both in emacs-26 and master.

BAD_TAGS
Description: Binary data

no_ext_ruby_test
Description: Text document

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#30075: etags misdetects ruby sharp-bang sequence
>
>
>
>
> Date: 
>
> Fri, 12 Jan 2018 01:50:41 +0300
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Thunderbird/58.0
>
>
>
>
> On 1/12/18 1:07 AM, Dmitry Gutov wrote:
> > On 1/11/18 7:39 PM, Eli Zaretskii wrote:
> >
> > > No one taught etags the name(s) of the Ruby interpreter(s), and nobody
> > > told it about the "#!/usr/bin/env FOO" way of specifying an interpreter.
> > >
> > > Should be fixed now on the emacs-26 branch.
> >
> > Looks fixed, thank you!
>
> Closing.
>
>
> --- End Message ---