From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: spwhitton@spwhitton.name, emacs-devel@gnu.org
Subject: Re: Missing entries for Perl in etags-regen-file-extensions -- okay for emacs-30?
Date: Fri, 20 Sep 2024 22:11:46 +0300 [thread overview]
Message-ID: <86o74i5edp.fsf@gnu.org> (raw)
In-Reply-To: <10dd3554-4249-41d1-864d-30cab687da6a@gutov.dev> (message from Dmitry Gutov on Fri, 20 Sep 2024 21:20:59 +0300)
> Date: Fri, 20 Sep 2024 21:20:59 +0300
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> >>> We already have "pl" in the list. Adding "pm" is okay, but then why
> >>> only it? why not add all the extensions that 'etags' supports?
>
> Adding "pm" sounds good.
>
> "All supported extensions" (or most) might be a good idea as well.
So I think we should add all of them on emacs-30.
> As long as the additions are not misdetected often - false positives
> based on obscure languages might be a nuisance.
Agreed. But it sounds like the only such case is .m, which could be
Mercury, not just ObjC.
> >> Okay thanks, I'll add "pm" so we don't have just one Perl extension, and
> >> hopefully we can figure out a better solution for master.
> > My question about adding more extensions was for emacs-30.
> >
> > Let's wait for Dmitry to chime in, and take it from there.
>
> The reason why is that etags parses files with unknown extensions as
> Fortran sources, and there is currently no opt-out. See this thread:
>
> https://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00323.html
>
> The same issue stops us from benefiting from etags' hashbang detection.
Right. These require to explicitly specify --language on the etags
command line. So maybe etags-regen could learn to apply special
command-line options to files matching a regexp. Or maybe we should
add an option to etags to disable the fallback to Fortran.
next prev parent reply other threads:[~2024-09-20 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 9:15 Missing entries for Perl in etags-regen-file-extensions -- okay for emacs-30? Sean Whitton
2024-09-20 10:34 ` Eli Zaretskii
2024-09-20 13:39 ` Sean Whitton
2024-09-20 13:41 ` Eli Zaretskii
2024-09-20 18:20 ` Dmitry Gutov
2024-09-20 19:11 ` Eli Zaretskii [this message]
2024-09-20 19:35 ` Dmitry Gutov
2024-09-20 19:59 ` Dmitry Gutov
2024-09-21 7:03 ` Eli Zaretskii
2024-09-21 13:48 ` Dmitry Gutov
2024-09-21 15:14 ` Eli Zaretskii
2024-09-22 1:09 ` Dmitry Gutov
2024-09-22 5:19 ` Eli Zaretskii
2024-09-23 16:57 ` Dmitry Gutov
2024-09-23 18:14 ` Eli Zaretskii
2024-09-23 18:24 ` Dmitry Gutov
2024-09-23 18:35 ` Dmitry Gutov
2024-09-23 17:07 ` Corwin Brust
2024-09-23 18:19 ` Eli Zaretskii
2024-09-23 18:28 ` Dmitry Gutov
2024-09-23 18:38 ` Eli Zaretskii
2024-09-23 18:39 ` Corwin Brust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86o74i5edp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.