From: Mike Ralphson <mike.ralphson@gmail.com>
To: Jeff King <peff@peff.net>, Roel Kluin <roel.kluin@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] git-cget: prints elements of C code in the git repository
Date: Tue, 24 Mar 2009 14:38:06 +0000 [thread overview]
Message-ID: <e2b179460903240738x272c884q62a666931ce99c2f@mail.gmail.com> (raw)
In-Reply-To: <20090324135906.GA10644@coredump.intra.peff.net>
2009/3/24 Jeff King <peff@peff.net>:
> Wouldn't it be a lot easier to base this on something like ctags, which
> already knows how to do all the parsing of C quirky C?
>
> I.e.:
>
> git ls-files | xargs ctags
> vi -t get_sha1
>
> Where you can replace "vi" with your editor of choice.
This kind of pipeline has the benefit that it can actually work on the
*repository*, and not just the working copy (as per the posted
script).
Although this kind of tool might be useful (I might even use it myself
for working on git, rather than as *part of git* on my other projects,
which are not written in C), it's a bit tangential even for contrib/
isn't it?
> And if you really like getting the definition dumped to stdout,
> writing a command-line viewer for the ctags format would be
> quite simple (and I would be surprised if one hasn't been
> written already).
http://users.telenet.be/bdr/pub/cshow/ ?
Mike
next prev parent reply other threads:[~2009-03-24 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:09 [PATCH] git-cget: prints elements of C code in the git repository Roel Kluin
2009-03-24 12:05 ` Johannes Schindelin
2009-03-24 13:30 ` Roel Kluin
2009-03-24 13:52 ` Johannes Schindelin
2009-03-24 15:08 ` Ping Yin
2009-03-24 13:59 ` Jeff King
2009-03-24 14:04 ` Stefan Karpinski
2009-03-24 14:05 ` Johannes Schindelin
2009-03-24 14:38 ` Mike Ralphson [this message]
2009-03-24 14:56 ` Johannes Schindelin
2009-03-24 16:37 ` Mike Ralphson
2009-03-24 16:33 ` Steven Tweed
2009-03-25 4:23 ` Jeff King
2009-03-24 16:17 ` roel kluin
2009-03-27 9:22 ` roel kluin
2009-03-27 11:26 ` Johannes Schindelin
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=e2b179460903240738x272c884q62a666931ce99c2f@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=roel.kluin@gmail.com \
/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 NNTP newsgroup(s).