From: Peter Lee <pete_lee@swbell.net>
Subject: Re: etags
Date: Thu, 19 Jun 2003 17:42:06 GMT [thread overview]
Message-ID: <uvfv2c6c2.fsf@swbell.net> (raw)
In-Reply-To: mailman.8237.1056026853.21513.help-gnu-emacs@gnu.org
>>>> Kevin Dziulko writes:
Kevin> Thanks for your reply, but "grep -n "^#define" *.c" isn't
Kevin> even close to what I'm looking for. I don't want a list of
Kevin> #define'ed constants, but rather #define'ed constants *THAT
Kevin> ACTUALLY GET USED*. That's why in my example I just wanted
Kevin> "Line 7: MSG1" and nothing about CONST1 to ever get
Kevin> listed. [also, I only want defines from my local program
Kevin> listed, and not any of the system library defines]. The
Kevin> cxref command is the closest to this that I've found thus
Kevin> far.
Seems like with a little lisp you could take the output of the above
grep and put it in a buffer. Then using a regex pattern to match your
actual constant, on that buffer, perform a grep on each one appending
the output to a seperate buffer.
Or you could do the above and if grep returns nothing for a given
constant, put that constant in a buffer... when it's done then all you
have is a list of constants that are *not* used and can then infer
that all others must be used somewhere.
next parent reply other threads:[~2003-06-19 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8237.1056026853.21513.help-gnu-emacs@gnu.org>
2003-06-19 17:42 ` Peter Lee [this message]
2004-10-06 2:18 etags moheb missaghi
[not found] <mailman.8073.1055852045.21513.help-gnu-emacs@gnu.org>
2003-06-19 9:36 ` etags Alan Mackenzie
2003-06-19 12:47 ` etags Kevin Dziulko
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 12:09 etags Kevin Dziulko
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=uvfv2c6c2.fsf@swbell.net \
--to=pete_lee@swbell.net \
/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).