GNU bug report logs - #67687
Feature request: automatic tags management

Previous Next

Full log

Message #110 received at 67687 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dmitry <at> gutov.dev>
Cc: 67687 <at> debbugs.gnu.org, eskinjp <at> gmail.com, michael.albinus <at> gmx.de,
 stefankangas <at> gmail.com
Subject: Re: bug#67687: Feature request: automatic tags management
Date: Sun, 31 Dec 2023 18:42:55 +0200

> Date: Sun, 31 Dec 2023 17:25:35 +0200
> Cc: eskinjp <at> gmail.com, 67687 <at> debbugs.gnu.org, michael.albinus <at> gmx.de
> From: Dmitry Gutov <dmitry <at> gutov.dev>
> 
> On 31/12/2023 08:34, Eli Zaretskii wrote:
> >> +Note that this feature disables itself if you have already manually
> >> +visited a tags table (with @kbd{M-x visit-tags-table}, or through an
> >> +explicit prompt triggered by some feature that requires tags).
> > This aspect is IMO somewhat problematic.  I wasn't aware of it, and
> > now that I read this, I'm not sure it is correct and will meet user
> > expectations.
> 
> I'm pretty sure you asked for it: that even when this mode is on, it 
> shouldn't interfere with completion tables explicitly visited by the user.

"Interfere" and "prevent automatic regeneration" is not the same.

I think this probably warrants a separate defcustom: some people might
want such regeneration, even if the tags table was loaded manually,
others won't.  And I think the default should be to regenerate them
regardless.

> And either way it seems like a prerequisite for enabling 
> etags-regen-mode by default sometimes in the future.

How so?  The fact that I loaded TAGS doesn't necessarily mean I don't
want it updated when the sources change.  Or what am I missing?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.