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

Previous Next

Full log

View this message in rfc822 format

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: bug#67687: Feature request: automatic tags management
Date: Mon, 01 Jan 2024 18:50:34 +0200

> Date: Mon, 1 Jan 2024 17:47:09 +0200
> Cc: stefankangas <at> gmail.com, eskinjp <at> gmail.com, 67687 <at> debbugs.gnu.org,
>  michael.albinus <at> gmx.de
> From: Dmitry Gutov <dmitry <at> gutov.dev>
> 
> > I guess for now it will be enough to document that invoking
> > visit-tags-table disables the mode for that project.  AFAICT this is
> > not currently documented anywhere in the patch.
> 
> OK, added a paragraph to the mode's docstring.
> [...]
> +
> +The exception is made when the user has already selected a tags
> +table manually (for example, using \\[visit-tags-table]).  Then
> +this mode doesn't do anything.  Reset the visited tags tables
> +using \\[tags-reset-tags-tables]."

The above is only true for the project whose TAGS was manually
visited, right?  IOW, it's not that once the use invokes
visit-tags-table once, this mode will be effectively disabled for the
entire session, right?

If so, I suggest to make it clear:

  If you select a tags table manually (for example, using
  \\[visit-tags-table]), then this mode will be effectively disabled
  for the project or the directory tree from which the tags table was
  visited (the mode will still auto-regenerate tags tables for other
  projects and directory trees).  Use \\[tags-reset-tags-tables] to
  countermand the effect of a previous \\[visit-tags-table].

Otherwise, this LGTM, thanks.

Previous Next

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