unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: dmitry@gutov.dev, eskinjp@gmail.com, michael.albinus@gmx.de,
	67687@debbugs.gnu.org
Subject: bug#67687: Feature request: automatic tags management
Date: Sun, 31 Dec 2023 08:34:27 +0200	[thread overview]
Message-ID: <83v88e3moc.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmke2VZZNOCREYiZ8x7Vp6pHDhMYh+yAucOOhWiTBFAOzw@mail.gmail.com> (message from Stefan Kangas on Sat, 30 Dec 2023 12:56:38 -0800)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 30 Dec 2023 12:56:38 -0800
> Cc: eskinjp@gmail.com, 67687@debbugs.gnu.org, 
> 	Michael Albinus <michael.albinus@gmx.de>
> 
>  @menu
>  * Tag Syntax::          Tag syntax for various types of code and text files.
> -* Create Tags Table::   Creating a tags table with @command{etags}.
> +* Update Tags Table::   Creating a tags table automatically.
> +* Create Tags Table::   Creating a tags table manually with @command{etags}.
>  * Etags Regexps::       Create arbitrary tags using regular expressions.
>  @end menu

Please don't change the order of the sections.  "Create" should
precede "update", since the regen feature is optional.  If this order
requires some changes in how the text is written, please make those
changes, but putting "update" before "create" is illogical.  Also, the
description of "update" says "create", which is another brow-raising
factor.

> +@node Update Tags Table
> +@subsubsection Keeping Tags Tables up to date
> +
> +   The easiest way to manage tags tables is by enabling
> +@code{etags-regen-mode} (@kbd{M-x etags-regen-mode RET}).

It is too early to say this, because if we do, people will ask why
that mode is not turned on by default.  We may turn it on by default
some day (and then the text will need to be rearranged or rewritten),
but we are not there yet, so let's please not put the cart before the
horse, and let's describe etags-regen-mode as what it is: an optional
minor mode that was just added, and should yet withstand the test of
time before we consider recommending it as _the_ primary MO.

> +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.





  parent reply	other threads:[~2023-12-31  6:34 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 11:43 bug#67687: Feature request: automatic tags management Jon Eskin
2023-12-07 15:57 ` Dmitry Gutov
2023-12-07 19:57   ` Jon Eskin
2023-12-10  2:41     ` Dmitry Gutov
2023-12-10 11:38       ` Jon Eskin
2023-12-20 21:11         ` Jon Eskin
2023-12-21  0:24           ` Dmitry Gutov
2023-12-21  7:40             ` Eli Zaretskii
2023-12-21 16:46               ` Dmitry Gutov
2023-12-21 23:37                 ` Dmitry Gutov
2023-12-24  1:43                   ` Dmitry Gutov
2023-12-28  9:30                     ` Eli Zaretskii
2023-12-30  3:05                       ` Dmitry Gutov
2023-12-30  7:33                         ` Eli Zaretskii
2023-12-30 23:43                           ` Dmitry Gutov
2023-12-31  1:02                             ` Stefan Kangas
2023-12-31 23:29                               ` Dmitry Gutov
2024-01-02  0:40                                 ` Stefan Kangas
2024-01-02  1:31                                   ` Dmitry Gutov
2023-12-31  7:07                             ` Eli Zaretskii
2023-12-31 15:21                               ` Dmitry Gutov
2023-12-29 22:29                     ` Stefan Kangas
2023-12-30  1:50                       ` Dmitry Gutov
2023-12-30 20:31                         ` Stefan Kangas
2023-12-30 22:50                           ` Dmitry Gutov
2023-12-30 23:25                             ` Stefan Kangas
2023-12-30 23:58                               ` Dmitry Gutov
2023-12-31  7:23                                 ` Eli Zaretskii
2023-12-31 15:31                                   ` Dmitry Gutov
2023-12-29 22:17                 ` Stefan Kangas
2023-12-30  1:31                   ` Dmitry Gutov
2023-12-30 20:56                     ` Stefan Kangas
2023-12-30 23:23                       ` Dmitry Gutov
2023-12-31  0:03                         ` Stefan Kangas
2023-12-31  6:34                       ` Eli Zaretskii [this message]
2023-12-31  7:22                         ` Stefan Kangas
2023-12-31 15:22                           ` Dmitry Gutov
2023-12-31 15:25                         ` Dmitry Gutov
2023-12-31 16:42                           ` Eli Zaretskii
2023-12-31 17:53                             ` Dmitry Gutov
2023-12-31 19:27                               ` Eli Zaretskii
2024-01-01  1:23                                 ` Dmitry Gutov
2024-01-01 12:07                                   ` Eli Zaretskii
2024-01-01 15:47                                     ` Dmitry Gutov
2024-01-01 16:50                                       ` Eli Zaretskii
2024-01-01 17:23                                         ` Dmitry Gutov
2024-01-01 17:39                                           ` Eli Zaretskii
2024-01-01 18:48                                             ` Dmitry Gutov
2024-01-01 19:25                                               ` Eli Zaretskii
2024-01-02  1:40                                                 ` Dmitry Gutov
2024-01-04  1:56                                                   ` Dmitry Gutov
2024-01-02 10:41                               ` Francesco Potortì
2024-01-02 13:09                                 ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v88e3moc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67687@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eskinjp@gmail.com \
    --cc=michael.albinus@gmx.de \
    --cc=stefankangas@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).