From: "Javier Oviedo" <email_joviedo@yahoo.com>
Subject: Re: help with tags
Date: Wed, 30 Jul 2003 16:28:15 -0400 [thread overview]
Message-ID: <bg99is$avr$1@home.itg.ti.com> (raw)
In-Reply-To: 844r146ock.fsf@slowfox.is.informatik.uni-duisburg.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2170 bytes --]
I use imenu as well for looking within a current file. Speedbar was kind of
cool, but it does not support the capabilities that I mentioned...i would
have to use tags externally..
I think that I'll give your etags method a chance. Would still have to do
this for every sub-directory or does your 'find' method do this recursively?
Has anyone ever tried to make something like I was originally looking for? I
think that it would most naturally fit into ecb...instead of running the
tags externally, build in the feature to ecb.
Thanks.
--
Javier
"Kai Großjohann" <kai.grossjohann@gmx.net> wrote in message
news:844r146ock.fsf@slowfox.is.informatik.uni-duisburg.de...
> "Javier Oviedo" <email_joviedo@yahoo.com> writes:
>
> > Is there some utility that will let me automatically create this kind of
> > tag/project system given some path? Ideally it would support the
following
> > functionality:
> >
> > 1. Given a root dir, it would add all sub-directories(and files within)
to
> > this project.
> > 2. It would auto-update tags tables when/if a file is modified.
> >
> > I'm not sure if this is asking too much, but please let me know if there
is
> > anything that performs some or all of these features. Thanks in advance!
>
> I think you have to do it manually, but make is your friend.
>
> rm TAGS; touch TAGS
> find . -name '*.[hc]' -print | xargs etags -a
>
> These commands add all *.h and *.c files to the TAGS file. You need
> to rerun them whenever something big has changed. So you could just
> add these commands to your normal build process, for instance. After
> all, if something big has changed, you're going to build the program
> anyway to check if it still works...
>
> Note that small modifications are not a problem -- M-. is smart
> enough to look around if the position information in TAGS is slightly
> off.
>
> You might also like the Emacs Code Browser and the Semantic
> Bovinator. The latter has some code parsers which give you tags-like
> functionality, and the former provides a GUI.
>
> Also, see M-x speedbar RET and also M-x imenu RET. I use M-x imenu
> RET a lot to jump around in the same file.
> --
> ~/.signature
next prev parent reply other threads:[~2003-07-30 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 14:00 help with tags Javier Oviedo
2003-07-30 15:11 ` Kai Großjohann
2003-07-30 20:28 ` Javier Oviedo [this message]
2003-07-31 17:02 ` Kai Großjohann
2003-07-31 6:43 ` Eli Zaretskii
[not found] ` <mailman.754.1059630121.8231.help-gnu-emacs@gnu.org>
2003-08-01 14:00 ` Javier Oviedo
2003-08-01 15:41 ` Dan Katz
-- strict thread matches above, loose matches on Subject: below --
2013-08-27 12:59 Help " Glen Stark
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='bg99is$avr$1@home.itg.ti.com' \
--to=email_joviedo@yahoo.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.
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).