Re: Missing entries for Perl in etags-regen-file-extensions -- okay for emacs-30?

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 20 Sep 2024 22:59:35 +0300
> From: Dmitry Gutov <dmitry@gutov.dev>
> Cc: spwhitton@spwhitton.name, emacs-devel@gnu.org
> 
> On 20/09/2024 22:35, Dmitry Gutov wrote:
> >>> 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.
> > 
> > I have no objections, if you're sure about misdetecion. Though note that 
> > the current logic only supports specifying extensions. So no Makefile/ 
> > Rakefile/etc.
> 
> Maybe do that on master, though.

Why on master? what's the danger of doing this on the release branch?
No code is changed, only data, and it only affects the files that
etags would tag anyway.

> Scanning for tags in files that aren't considered code like .html or 
> .texi, etc might create a lot more navigation locations, not all of them 
> wanted in 'C-u M-.' completion.
> 
> I'm not actually sure it will be a problem, but it seems like a major 
> enough change to allow for user feedback first.

But etags-regen is not only about completion, is it?  Its main
purpose, AFAIU, is to automatically regenerate tags tables when they
are outdated.  Or what am I missing?