Quoting Randy Kramer <[EMAIL PROTECTED]>:
> I'm trying to learn to use ctags (with nedit, to review the nedit source
> code), and have some questions:
>
> 1. I've got things working partially in that when I select a function, I
> can
> press <ctrl>d to get to the definition. I thought (or hoped) that I could
> also go the other way, that is from the definition jump to each place where
> the function was called. So far I can't do that. Is that a capability of
> ctags / nedit? (Is that a limitation in nedit?)
Ctags only finds where things are defined (or declared), not where they are
used. For that, with nedit, I find grep is usually sufficient.
> 2. So far I've been indexing the files using ctags with no command line
> switches. I suspect I should use some or all of the following:
>
> -d, --defines
> -g, --globals
> -m, --members
> -t, --typedefs
> -T, --typedefs-and-c++
>
> What do you use / recommend?
I use
ctags -e -R --excmd=pattern --extra=fq --fields=afiKmsSz \
--C-kinds=+cdefgmnpstuvx --C++-kinds=+cdefgmnpstuvx \
-o TAGS
which I think probably gives me just about everything. You do get multiple
entries for both definition and declaration, though, which may be annoying.
The emacs format (incompatible with vi) is less wasteful of diskspace.
> 3. Would Exuberant ctags provide any additional functionality?
Not that I know of.
Tony
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop
