GNU bug report logs - #30086
Please add a flag to stop etags from falling back to Fortran and C

Previous Next

Package: emacs;

Reported by: Dmitry Gutov <dgutov <at> yandex.ru>

Date: Fri, 12 Jan 2018 12:07:02 UTC

Severity: wishlist

To reply to this bug, email your comments to 30086 AT debbugs.gnu.org.

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#30086; Package emacs. (Fri, 12 Jan 2018 12:07:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Dmitry Gutov <dgutov <at> yandex.ru>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 12 Jan 2018 12:07:03 GMT) Full text and rfc822 format available.

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: Please add a flag to stop etags from falling back to Fortran and C
Date: Fri, 12 Jan 2018 15:06:08 +0300
Previous discussion here: 
http://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00323.html




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30086; Package emacs. (Fri, 12 Jan 2018 13:10:02 GMT) Full text and rfc822 format available.

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

From: Francesco Potortì <pot <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 30086 <at> debbugs.gnu.org
Subject: Re: bug#30086: Please add a flag to stop etags from falling back to
 Fortran and C
Date: Fri, 12 Jan 2018 14:09:40 +0100
>Previous discussion here: 
>http://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00323.html

I argue that fallbacks should be removed, or at least the default
reversed, i.e., not use fallback unless some --legacy-fallback option is
given.

Falbacks only make sense in an environment where Fortran and C are much
more prominently used than other languages AND where it is common to use
nonstandard suffixes for the source files.

Neither assumption is true nowadays, and I'd say it hasn't been true for
projects started in maybe the latest 20 years, while it may have been
true for legacy projects at the time when Etags was written.

Those legacy projects are the only reason why Etags should keep using a
default.  I assume that if people need to support Fortran or C
environments 20 years old without even changing the file name suffixes,
they are probably forced to use old tools, among which old Etag
versions, and we should not worry about such strict compatibility.

So, I'd say, just remove fallbacks, or use them only if a
--legacy-fallback option is used.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30086; Package emacs. (Fri, 12 Jan 2018 14:02:02 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Francesco Potortì <pot <at> gnu.org>
Cc: 30086 <at> debbugs.gnu.org, dgutov <at> yandex.ru
Subject: Re: bug#30086: Please add a flag to stop etags from falling back to
 Fortran and C
Date: Fri, 12 Jan 2018 16:00:09 +0200
> Date: Fri, 12 Jan 2018 14:09:40 +0100
> From: Francesco Potortì <pot <at> gnu.org>
> Cc: 30086 <at> debbugs.gnu.org
> 
> So, I'd say, just remove fallbacks, or use them only if a
> --legacy-fallback option is used.

The latter, of course (if the default is to change).




This bug report was last modified 7 years and 156 days ago.

Previous Next


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