From: Bart Veer <bartv@redhat.com>
To: jeff@datataker.com.au
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How best to create tags file for ecos source?
Date: Mon, 21 May 2001 05:54:00 -0000 [thread overview]
Message-ID: <200105211254.f4LCsAY30999@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <004d01c0e192$9dc322a0$2901a8c0@JEFF>
>>>>> "Jeff" == Jeff Lasslett <jeff@datataker.com.au> writes:
Jeff> I'm a vim user and I would really like to know the
Jeff> best way to create ctags file(s) for the ecos source. The
Jeff> problem is that I don't want to create tags for the whole
Jeff> source tree because it contains code for other platforms and
Jeff> it contains packages that I may not build into my project.
Jeff> I have tried manually running ctags for each directory
Jeff> that I want tags for but I think the tags file gets too big
Jeff> and vim takes forever to jump to a tagged item.
Jeff> If anyone has any advice for regarding this I would
Jeff> appreciate it.
I don't think there is an easy way to automate this at present. The
current makefile generation code does not provide any support for tags
generation. The knowledge of which files get built for a specific
configuration (including automatically generated files) is only
available to C++ programs linked with libcdl, and there is no
documentation for the libcdl API at present (other than the comments
in the header files).
In the medium to long term, I hope to make this sort of information
available to Tcl scripts. However I do not know when this is going to
happen.
Bart
prev parent reply other threads:[~2001-05-21 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 18:05 Jeff Lasslett
2001-05-21 5:54 ` Bart Veer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200105211254.f4LCsAY30999@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jeff@datataker.com.au \
/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).