From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: etags-regen-mode: handling extensionless files
Date: Wed, 25 Sep 2024 15:10:05 +0300
Message-ID: <86a5fwc4te.fsf@gnu.org>
References: <87tteaznog.fsf@zephyr.silentflame.com>
 <edab570c-b2fa-4162-9383-df5c8aaff251@yandex.ru>
 <8734lrrj4e.fsf@zephyr.silentflame.com>
 <ea10f340-9b46-4199-93fc-274c5e81ace4@yandex.ru>
 <87o74c1ce1.fsf@zephyr.silentflame.com>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="7497"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: dgutov@yandex.ru, emacs-devel@gnu.org
To: Sean Whitton <spwhitton@spwhitton.name>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 25 14:11:10 2024
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
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 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1stQrN-0001j3-Lz
	for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Sep 2024 14:11:09 +0200
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1stQqf-0006nO-92; Wed, 25 Sep 2024 08:10:26 -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 <eliz@gnu.org>) id 1stQqP-000642-IB
 for emacs-devel@gnu.org; Wed, 25 Sep 2024 08:10:10 -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 <eliz@gnu.org>)
 id 1stQqO-0002bT-Oe; Wed, 25 Sep 2024 08:10:08 -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=xoVB7ex34unzGixIDkmjate/4VIeg0+fz2QCi5Sp3b4=; b=RqYIljcVl6Fr
 zwUNKjFqb00H9fKB01aZE9c/K1Y/U7+618f8eKc74qLHdO21zV4fSf2AQ7GZ+K0MgP+4a6sS96OCD
 cjEyVPuqyZY5Lmo5wT+3ShqvK/qchU8jXtcd4gazbfA4eBpCa484mt1CufpOfe46f3R+WmbwheQnY
 L8qA/3YSCvU+MVWOf+JVzXA/LcsN9udShTRjARsemMGSRrjQDCMFcPcYTXA7OT2nZegHzwI9Flqov
 /C4T3U/h/hzpOp0SCoC5zTfMSShHoNPMOupCyFzj/Dn+H8qNSsH1iZc8h1zAldc3BKkLerSV2E3v9
 qpYuXv8u+3k6UG6MOW5M7Q==;
In-Reply-To: <87o74c1ce1.fsf@zephyr.silentflame.com> (message from Sean
 Whitton on Wed, 25 Sep 2024 07:21:58 +0100)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=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:324064
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/324064>

> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: emacs-devel@gnu.org
> Date: Wed, 25 Sep 2024 07:21:58 +0100
> 
> Hello,
> 
> On Mon 23 Sep 2024 at 08:00pm +03, Dmitry Gutov wrote:
> 
> > On 22/09/2024 15:02, Sean Whitton wrote:
> >
> >>> But see my other email regarding etags' hashbang detection.
> >> Hashbang detection would solve my problem elegantly.
> >> Is my reading of the other thread correct that if we can fix the fortran
> >> fallback then we can enable the hashbang detection?
> >
> > Yep, I think so.
> >
> > We would probably also discuss etags' auto-detection and its list of default
> > extensions, during the next release's development.
> 
> Okay, cool!  Should we have a bug to track this?

We could, but adding an option to disable the Fortran fallback is so
easy that I hope someone will just do it...