From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] something like cscope/cbrowser?
Date: Mon, 27 Mar 2006 18:08:40 -0500 [thread overview]
Message-ID: <0029edc1a42eca0d6dab99db940f96ca@coraid.com> (raw)
In-Reply-To: <4428649C.2090207@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
I use acme and the rc function `g' or small permutations of it.
fn g {grep -n $* *.[chsyl] /dev/null}
For just looking at headers I just change the function a bit.
fn gh {grep -n $* *.h /dev/null}
Then I can just click on the file:line and Whammo, I'm there.
[-- Attachment #2: Type: message/rfc822, Size: 8555 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 567 bytes --]
Hi,
it's not a plan9-only question... but here read many developers with
expertise. At work, dealing with big amounts of code (most of them
unknown to me), I've found the pair "cscope" and "cbrowser" really
helpful, even with C++ code. I'm wondering what do you usually use.
I likely want to avoid beliving every developer using plan9 uses acme
with greps in it. :)
btw, even vim is always my editor, cbrowser and acme made me acknowledge
that using keys for coding is not faster than using mostly a mouse
acme-style.
Thanks in advance,
Lluís
[-- Attachment #2.1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]
next prev parent reply other threads:[~2006-03-27 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 22:18 Lluís Batlle i Rossell
2006-03-27 22:28 ` Steve Simon
2006-03-27 23:08 ` Brantley Coile [this message]
2006-03-30 17:38 ` rog
2006-04-03 10:51 ` Abhey Shah
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=0029edc1a42eca0d6dab99db940f96ca@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.edu \
/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).