From: Luca Ferrari <fluca1978@infinito.it>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: etags not working properly
Date: Tue, 27 Aug 2013 08:46:42 +0200 [thread overview]
Message-ID: <CAKoxK+7jy24rdCXz+dOCpqXiarYbDHccPLJLBSo4A-q7qTO61g@mail.gmail.com> (raw)
Hi all,
I'm trying to using etags against a quite larger project, the FreeBSD
source tree. What I've done is as follows:
cd /usr/src && find . -name '*.[ch]' -print0 | xargs -0 etags
After that, if I try to lookup (M-.) any tag, even the simpler and
common one, I got screwed: etags points me to another wrong location
or does not point me anywhere. For instance, "struct vmspace" is not
found, "struct vnode" points me to provnode, "struct rusage" points me
to a completely different #define, and so on.
Am I indexing the source tree in the wrong way?
I'm using emacs 24.3.1 with the associated etags.
Thanks,
Luca
next reply other threads:[~2013-08-27 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 6:46 Luca Ferrari [this message]
2013-08-27 15:14 ` etags not working properly Eli Zaretskii
2013-08-28 6:44 ` Luca Ferrari
2013-08-28 14:48 ` Eli Zaretskii
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=CAKoxK+7jy24rdCXz+dOCpqXiarYbDHccPLJLBSo4A-q7qTO61g@mail.gmail.com \
--to=fluca1978@infinito.it \
--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).