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: Sun, 22 Sep 2024 08:19:38 +0300 [thread overview]
Message-ID: <86cykw2rkl.fsf@gnu.org> (raw)
In-Reply-To: <a879bf4d-87b8-4db4-84cd-ee505dcf7efa@gutov.dev> (message from Dmitry Gutov on Sun, 22 Sep 2024 04:09:22 +0300)
> Date: Sun, 22 Sep 2024 04:09:22 +0300
> Cc: spwhitton@spwhitton.name, emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 21/09/2024 18:14, Eli Zaretskii wrote:
>
> > If you have reservations about some of the extensions, let's exclude
> > them for now. I believe there are just a few of them, while the vast
> > majority should present no problem, right? I'm okay with leaving out
> > HTML and Texinfo. Are there more of those? TeX, perhaps?
>
> TeX yes. I'm also not sure about PostScript - but really because I still
> don't know how a function definition in that language looks, even after
> skimming through a manual.
>
> Speaking of other extensions, isn't ".a" usually a compiled library
> rather than ASM source code? Also curious about ".t" for Scheme and
> ".ml" for Lisp.
Fine, let's exclude all of these. It still leaves quite a lot.
> Not much else jumps out, but if somebody else has suggestions what to
> remove, we should probably do so (for the release branch). Basically,
> whatever extensions that might be not very common for a given language
> and could create false hits.
Agreed.
next prev parent reply other threads:[~2024-09-22 5:19 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cykw2rkl.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).