Subject: bug#30075: closed (Re: bug#30075: etags misdetects ruby sharp-bang sequence)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 11 Jan 2018 22:51:02 +0000

Your bug report

#30075: etags misdetects ruby sharp-bang sequence

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
30075: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30075
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#30075: etags misdetects ruby sharp-bang sequence
From: Dmitry Gutov <[email-masked]>
To: [email-masked]
Date: Fri, 12 Jan 2018 01:50:41 +0300
List-Id: <debbugs-submit.debbugs.gnu.org>

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.

Subject: etags misdetects ruby sharp-bang sequence
From: Dmitry Gutov <[email-masked]>
To: [email-masked]
Date: Thu, 11 Jan 2018 02:36:55 +0300
List-Id: <debbugs-submit.debbugs.gnu.org>

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.