From: Pete Wyckoff <pw@osc.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ctags as generated by make tags
Date: Tue, 29 May 2001 13:21:24 -0400 [thread overview]
Message-ID: <20010529132124.B13723@osc.edu> (raw)
In-Reply-To: <20010528233004.E3107@somanetworks.com>
In-Reply-To: <20010528233004.E3107@somanetworks.com>; from mark@somanetworks.com on Mon, May 28, 2001 at 11:30:04PM -0400
mark@somanetworks.com said:
> Anyone have any good tips on getting tags to generate nicely?
>
> I'm having some problems with some tags for macros and such being
> declared in several places since ctags doesn't honour any CPP #if'ing.
> I've currently got my Makefile doing this, which seems to give me some
> sanity as the redefinitions tend to be made by drivers and such.
Like net_device gets redefined or typedefed in a bunch of drivers
striving for backward compatibility.
> I'm basically walking the include tree by depth without doing any sorting
> of tags and then doing a stable sort on the final tags file.
I wrote a little perl script to post-process the tags file to sort
duplicate entries that are "more important" to the top, where that means
struct >> typedef >> union >> ... >> #define >> ...
So vim goes to the "real" definition of net_device first, before any of
the overridies in the drivers.
See http://www.osc.edu/~pw/index.html#tags for the script, and a
more complete set of ignores.
-- Pete
prev parent reply other threads:[~2001-05-29 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 3:30 ctags as generated by make tags Mark Frazer
2001-05-29 17:21 ` Pete Wyckoff [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=20010529132124.B13723@osc.edu \
--to=pw@osc.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.