From: Bastian Beischer <bastian.beischer@rwth-aachen.de>
To: Xavier Noria <fxn@hashref.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: best practices for TAGS
Date: Mon, 5 Dec 2011 19:39:19 +0100 [thread overview]
Message-ID: <CAK9AuB9xF8ySX8UJobXv+SGVH7xts6vd-R1DnXTBHfKdszmK9A@mail.gmail.com> (raw)
In-Reply-To: <CAM=Ycdh3r7hFGgy0O+S6PGFrEgzpK+y6gKQnEgWetJHm7oZ-5Q@mail.gmail.com>
I use etags-table which assigns TAGS files to my projects and GNU Make
rules to update the TAGS file when I run make... The suggested
algorithms to update it always might work better, though.
On Mon, Dec 5, 2011 at 12:29 AM, Xavier Noria <fxn@hashref.com> wrote:
> I would basically like to have a workflow for the TAGS file that makes
> some assumptions, and thanks to them it works out of the box and it is
> always in sync.
>
> For example, define the current tags file as the first one you find
> from the current directory up the hierarchy, nil if none found.
>
> I'd like to define my own version of find-tag that looks for the
> current tags file as defined above.
>
> If the tags file is outdated, I'd like to run some shell command
> automatically and revisit it, then do the find-tag.
>
> No prompts whatsoever. If I find myself in a situation where the
> conventions do not hold, I'll resort to the builtin functions.
>
> You see, I'd like that find-tag and friends do automatically what
> makes sense in 99% of my projects and be always in sync without my
> intervention.
>
> Does anybody work use a worflow like that?
>
--
Bastian Beischer
I. Physikalisches Institut B (RWTH Aachen)
Sommerfeldstr. 14
52074 Aachen
GERMANY
Office: 28-C-203
Phone: +49 241 - 8027205
prev parent reply other threads:[~2011-12-05 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 23:29 best practices for TAGS Xavier Noria
2011-12-04 23:36 ` Xavier Noria
2011-12-06 2:20 ` Philipp Haselwarter
2011-12-05 6:28 ` Peter Münster
2011-12-05 18:39 ` Bastian Beischer [this message]
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=CAK9AuB9xF8ySX8UJobXv+SGVH7xts6vd-R1DnXTBHfKdszmK9A@mail.gmail.com \
--to=bastian.beischer@rwth-aachen.de \
--cc=fxn@hashref.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).