From: Tom Tromey <tom@tromey.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: mctags
Date: Sat, 21 Oct 2017 13:59:30 -0600 [thread overview]
Message-ID: <87y3o4qnkt.fsf@tromey.com> (raw)
In-Reply-To: <jwvbmlbxjlv.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Fri, 13 Oct 2017 09:42:32 -0400")
>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
Stefan> So I think the better answer is to let the user teach etags.el how to
Stefan> create the TAGS file in such special cases (i.e. it can have a default
Stefan> system, based on *.o thingies or based on VCS data, but that can be
Stefan> overridden on a per-project basis, e.g. via .dir-locals.el).
I have some patches to etags (not etags.el) to do this.
The idea is to have a ".etags" config file that tells etags what to do.
Then "etags --find" will read this file, walk the directory tree, and
update the TAGS file.
Here's a sample config file based on what gdb's "make TAGS" currently
does:
# Ignore some test suite files.
!testsuite/*.[chylmsS]
# Ignore some other things.
!*.def
!*/Makefile*
# Handle DejaGNU (Tcl) files using regexps.
*.exp --language=none --regex='/\(gdb_caching_proc\|proc\|proc_with_prefix\)[ \t]+\([^ \t]+\)/\2/'
Making etags.el auto-update with this is simple: just run "etags --find".
It would also be easy to script this using inotify-tools.
This work still has some minor things to clean up. I didn't make
--include work (I think --find should stop at any subdirectory .etags it
finds, and then process those directories separately -- that is, include
should be automatically handled); and there's some argument validation
to be implemented.
If this sounds interesting, I can clean it up and send it.
Tom
next prev parent reply other threads:[~2017-10-21 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 11:05 [ELPA] New package: mctags Chen Bin
2017-10-12 12:11 ` Eli Zaretskii
2017-10-12 13:24 ` chen bin
2017-10-12 16:13 ` Eli Zaretskii
2017-10-13 1:39 ` chen bin
2017-10-13 8:47 ` Eli Zaretskii
2017-10-13 12:24 ` chen bin
2017-10-13 12:33 ` Dmitry Gutov
[not found] ` <CAAE-R+-Xxm3x5_u9jMO243SqfwaYfQs6XC=p1T0XQaAeFgy+dg@mail.gmail.com>
2017-10-14 0:52 ` Fwd: " chen bin
2017-10-13 13:42 ` Stefan Monnier
2017-10-21 19:59 ` Tom Tromey [this message]
2017-10-21 20:43 ` Stefan Monnier
2017-10-25 15:11 ` Tom Tromey
2017-11-12 3:19 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2017-10-07 1:39 Chen Bin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3o4qnkt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.