9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Abhey Shah <as234@york.ac.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] something like cscope/cbrowser?
Date: Mon,  3 Apr 2006 11:51:49 +0100	[thread overview]
Message-ID: <98d999bc8828ba03194c84e4d14d4930@york.ac.uk> (raw)
In-Reply-To: <0029edc1a42eca0d6dab99db940f96ca@coraid.com>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

Hello,
In inferno acme I've edited /acme/edit/guide, so one line is
  e '.b:0,$' | x '/^[a-z]*\([a-zA-Z,: ]*\)[a-z :]+{\n/' | ./p -n
This gives me a clickable list of all the functions in limbo files I 
have open. Also in the same file is e 'Errors:0,$' | c'' which clears 
the window I just made with all the function names.
You can do similiar things with plan 9 acme and I'd actually be curious 
to see the contents of anybody else guide file.

Abhey
>
> From: Lluís Batlle i Rossell <viriketo@gmail.com>
> Date: 27 March 2006 23:18:04 BST
> To: 9fans Mailing list <9fans@cse.psu.edu>
> Subject: [9fans] something like cscope/cbrowser?
> Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
>
>
> 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: Type: text/plain, Size: 296 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Transfer-Encoding: quoted-printable
	Content-Type: text/enriched;
	charset=ISO-8859-1

[-- Attachment #2.2: file.suspect --]
[-- Type: application/octet-stream, Size: 1616 bytes --]

Hello,

In inferno acme I've edited /acme/edit/guide, so one line is 

 e '.b:0,$' | x '/^[a-z]*\([a-zA-Z,: ]*\)[a-z :]+{\n/' | ./p -n

This gives me a clickable list of all the functions in limbo files I
have open. Also in the same file is e 'Errors:0,$' | c'' which clears
the window I just made with all the function names.

You can do similiar things with plan 9 acme and I'd actually be
curious to see the contents of anybody else guide file.  


Abhey

<excerpt><bold><color><param>0000,0000,0000</param>

From: </color></bold>Lluís Batlle i Rossell <<viriketo@gmail.com>

<bold><color><param>0000,0000,0000</param>Date: </color></bold>27
March 2006 23:18:04 BST

<bold><color><param>0000,0000,0000</param>To: </color></bold>9fans
Mailing list <<9fans@cse.psu.edu>

<bold><color><param>0000,0000,0000</param>Subject: </color>[9fans]
something like cscope/cbrowser?

<color><param>0000,0000,0000</param>Reply-To: </color></bold>Fans of
the OS Plan 9 from Bell Labs <<9fans@cse.psu.edu>



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



</excerpt> 

      parent reply	other threads:[~2006-04-03 10:51 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
2006-03-30 17:38   ` rog
2006-04-03 10:51   ` Abhey Shah [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=98d999bc8828ba03194c84e4d14d4930@york.ac.uk \
    --to=as234@york.ac.uk \
    --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).