From: Dmitry Gutov <dgutov@yandex.ru>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Generation of tags for the current project on the fly
Date: Thu, 18 Jan 2018 03:14:49 +0300 [thread overview]
Message-ID: <1fad0c79-cd65-df83-9dcc-2650fed4dad1@yandex.ru> (raw)
In-Reply-To: <877esgqdhk.fsf@tromey.com>
On 1/18/18 02:20, Tom Tromey wrote:
> Dmitry> ctags supports incremental updates?
>
> Yeah, see "-u" in "ctags --help":
Cool. This is probably from Universal Ctags. Still not in Ubuntu (17.04,
at least).
> -u, --update
> Update the tag entries for the given files, leaving tag
> entries for other files in place. Currently, this is
> implemented by deleting the existing entries for the given
> files and then rewriting the new entries at the end of the
> tags file. It is often faster to simply rebuild the entire
> tag file than to use this.
Seems like it updates the file in place. And your implementation copies
the entries and allocates a new file. Any difference in performance that
you noticed?
> Dmitry> The config file duplicates some info in .gitignore and
> Dmitry> project-vc-ignores, though. Which is unfortunate.
>
> True, but there are two reasons for this. One, there are still several
> version control systems in use, and I didn't want to try to parse every
> config file.
I think it should work like:
git ls-files | etags -
Replace 'git ls-files' with an appropriate incantation for each VCS.
> Second, sometimes a generated file will be checked in, but
> you might still want to omit it from TAGS -- so some mechanism like this
> is needed.
Yup. This seems to work (excluding .clang_format; there's also an option
to read additional ignores from a file):
git ls-files -cdmo --exclude-standard -x .clang-format | etags -
> Dmitry> I also doubt that 'make tags' will go away anytime soon.
>
> Sure, me too, but this approach is taken by more tools nowadays, and it
> can live alongside "make tags".
Is that true? The modern tools have taken the approach of duplicating
the ignore lists?
> Dmitry> Any chance your code supports something analogous to 'global
> Dmitry> --single-update' (except with multiple file arguments, hopefully)?
> Dmitry> That's what I've been trying to describe.
>
> It could certainly be done without much effort.
Very good. Does it handle file deletions as well?
>>> I suppose I could push my branch to git if that would be convenient.
>>> Just let me know.
>
> Dmitry> I'm sure it would be helpful, even if only to study the approach.
>
> I pushed it to feature/etags-update.
Thanks! I'll do some benchmarking if nobody beats me to it.
next prev parent reply other threads:[~2018-01-18 0:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 1:02 Generation of tags for the current project on the fly Dmitry Gutov
2018-01-12 9:01 ` Eli Zaretskii
2018-01-12 13:52 ` Dmitry Gutov
2018-01-12 18:52 ` Eli Zaretskii
2018-01-14 2:05 ` Dmitry Gutov
2018-01-14 16:21 ` Eli Zaretskii
2018-01-15 1:44 ` Dmitry Gutov
2018-01-15 5:37 ` Eli Zaretskii
2018-01-15 18:50 ` Dmitry Gutov
2018-01-16 17:50 ` Eli Zaretskii
2018-01-16 21:56 ` Dmitry Gutov
2018-01-17 15:40 ` Eli Zaretskii
2018-01-17 19:43 ` Dmitry Gutov
2018-01-17 20:12 ` Eli Zaretskii
2018-01-17 22:19 ` Dmitry Gutov
2018-01-17 22:28 ` Dmitry Gutov
2018-01-17 22:02 ` Tom Tromey
2018-01-17 22:44 ` Dmitry Gutov
2018-01-17 23:20 ` Tom Tromey
2018-01-18 0:14 ` Dmitry Gutov [this message]
2018-01-18 1:30 ` Dmitry Gutov
2018-01-19 1:21 ` Dmitry Gutov
2018-01-20 22:15 ` Tom Tromey
2018-01-20 23:57 ` Tom Tromey
2018-01-21 12:26 ` Dmitry Gutov
2018-01-30 4:45 ` Tom Tromey
2018-02-04 23:32 ` Dmitry Gutov
2018-01-30 5:05 ` Tom Tromey
2018-02-04 23:40 ` Dmitry Gutov
2018-02-05 17:06 ` Eli Zaretskii
2018-02-05 20:10 ` Dmitry Gutov
2018-02-06 19:36 ` Eli Zaretskii
2018-02-06 20:41 ` Dmitry Gutov
2018-02-07 3:26 ` Eli Zaretskii
2018-02-07 9:47 ` Dmitry Gutov
2018-02-07 21:30 ` Tom Tromey
2018-02-09 9:41 ` Dmitry Gutov
2018-02-08 20:31 ` John Yates
2018-02-09 0:22 ` Dmitry Gutov
2020-12-08 22:26 ` Dmitry Gutov
2018-01-17 11:08 ` Dmitry Gutov
2018-01-15 1:50 ` John Yates
2018-01-15 5:42 ` Eli Zaretskii
2018-01-15 15:01 ` Dmitry Gutov
2018-01-15 17:21 ` Eli Zaretskii
2018-01-15 17:45 ` Dmitry Gutov
2018-01-15 20:56 ` Matthias Meulien
2018-01-15 21:44 ` Dmitry Gutov
2018-01-15 16:33 ` John Yates
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=1fad0c79-cd65-df83-9dcc-2650fed4dad1@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.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).