From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Missing entries for Perl in etags-regen-file-extensions -- okay for emacs-30? Date: Sat, 21 Sep 2024 18:14:52 +0300 Message-ID: <86sett2g43.fsf@gnu.org> References: <87y13mznw9.fsf@zephyr.silentflame.com> <86h6aa7gw1.fsf@gnu.org> <87ploya1hc.fsf@zephyr.silentflame.com> <867cb67888.fsf@gnu.org> <10dd3554-4249-41d1-864d-30cab687da6a@gutov.dev> <86o74i5edp.fsf@gnu.org> <690fff1d-b8f2-4e6e-b105-21ca97a0a92e@gutov.dev> <86ldzl5vzj.fsf@gnu.org> <3b153949-c990-49c9-9618-28850d3ee57c@gutov.dev> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spwhitton@spwhitton.name, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 21 17:15:35 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ss1pf-0001A3-Cx for ged-emacs-devel@m.gmane-mx.org; Sat, 21 Sep 2024 17:15:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ss1p3-0004x6-Hl; Sat, 21 Sep 2024 11:14:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ss1p1-0004wu-Cb for emacs-devel@gnu.org; Sat, 21 Sep 2024 11:14:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ss1p0-0002jE-VH; Sat, 21 Sep 2024 11:14:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=nmLC0M/VcUwTCCvBW+3QCpGB4WQjmNIZHx0xIQZvVDg=; b=Opjk1R3n5mv7 qoqmDoZ+YaFWBHCZYeaHeKLM+r720eFJCk17g2EGkzec6suY3nVdS161RWsA/YVEygQchvXL70j6V zn9c12YTVEy7KMNZnECp+uQhtDTkvHeVDHcjC2vE5YJeDIDrOwXiul5lH9mbLZh09ZCRxC5C0B69l oo9NcKlG/PS/jIFNNU/ZF5OHQuFb5zLs13kXwMY31e8fASl7IIh3IwUf8CleDWCgNXtKLwfQao5GM S6h8auKthfzV0KaeBLEjM4Y37RppQ/btt5o5lv+OP/iP1mZ+sBto3UGgRWyn7on8VA3XvxDuD82vB E5/e7qVR+BnyAeFbB+fRGw==; In-Reply-To: <3b153949-c990-49c9-9618-28850d3ee57c@gutov.dev> (message from Dmitry Gutov on Sat, 21 Sep 2024 16:48:22 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:323895 Archived-At: > Date: Sat, 21 Sep 2024 16:48:22 +0300 > Cc: spwhitton@spwhitton.name, emacs-devel@gnu.org > From: Dmitry Gutov > > On 21/09/2024 10:03, Eli Zaretskii wrote: > > >> 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? > > I've never generated tags for HTML or Texinfo files, and didn't really > think about it as an option. Do you? 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? > So I suggest drawing the line somewhere between tags for text and tags > for code. We can add all the programming file extensions in emacs-30 and > for 31 somebody might implement the "no Fortran fallback" option, so we > might drop the list of extensions altogether. We would have time to > restore it before the next release, though, if particular problems come > up (e.g. drop in performance). Fine by me, thanks.