GNU bug report logs - #30075
etags misdetects ruby sharp-bang sequence

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 30075 in the body.
You can then email your comments to 30075 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: bug-gnu-emacs <at> gnu.org
Subject: etags misdetects ruby sharp-bang sequence
Date: Thu, 11 Jan 2018 02:36:55 +0300

[Message part 1 (text/plain, inline)]

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 (application/octet-stream, attachment)]

[no_ext_ruby_test (text/plain, attachment)]

Message #8 received at 30075 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 30075 <at> debbugs.gnu.org
Subject: Re: bug#30075: etags misdetects ruby sharp-bang sequence
Date: Thu, 11 Jan 2018 18:39:01 +0200

> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Thu, 11 Jan 2018 02:36:55 +0300
> 
> 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.

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.

Thanks.

Message #11 received at 30075 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30075 <at> debbugs.gnu.org
Subject: Re: bug#30075: etags misdetects ruby sharp-bang sequence
Date: Fri, 12 Jan 2018 01:07:54 +0300

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!

Message #16 received at 30075-done <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: 30075-done <at> debbugs.gnu.org
Subject: Re: bug#30075: etags misdetects ruby sharp-bang sequence
Date: Fri, 12 Jan 2018 01:50:41 +0300

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.