From: Noel Hunt <noel.hunt@gmail.com>
To: Marcus Clark <marcus.e.clark@outlook.com>
Cc: TUHS <TUHS@tuhs.org>
Subject: [TUHS] Re: Does anyone have any memories of using cscope that they care to share?
Date: Fri, 5 Apr 2024 12:38:55 +1100 [thread overview]
Message-ID: <CAGfO01zTgj1QtKCBpjUSxeYphVwf221tEqnMeS_CL4wZSif=Aw@mail.gmail.com> (raw)
In-Reply-To: <LO2P123MB74066CA4C75C4E6FF10DA007D53C2@LO2P123MB7406.GBRP123.PROD.OUTLOOK.COM>
And don't forget that 'samuel' had an interface to 'cscope'.
The drawback to that is that 'samuel' tries to put cscope's output onto a
cacscaded button 3 menu, and when you have a large number of resuslts
this unfortunately becomes unwieldly. Samuel is extremely nice to use
when you aren't dealing with hundreds of results from a search.
By modifying cscope's output such that the filename/linenumber information
is in a saner format (i.e., 'filename:linenumber'), and is the first
field of the
output line, then it is possible to use cscope with Plan9-style plumbing (sam,
acme) by availing oneself of the line-oriented output format. This could, for
example, be read into an acme window.
On Fri, Apr 5, 2024 at 8:16 AM Marcus Clark <marcus.e.clark@outlook.com> wrote:
>
>
> Wikipedia has a brief page on cscope, which has a link to
> https://cscope.sourceforge.net/history.html
> written by Harold Bamford, in which he talks about the
> early days of cscope at Bell Labs and its inventor Joe Steffan.
>
> I wondered if anyone can add any interesting information about using
> cscope on their projects or anything about its development.
>
> -Marcus.
next prev parent reply other threads:[~2024-04-05 1:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 21:16 [TUHS] " Marcus Clark
2024-04-04 22:38 ` [TUHS] " Larry McVoy
2024-04-04 22:41 ` Dan Cross
2024-04-04 23:35 ` Greg 'groggy' Lehey
2024-04-05 1:37 ` Dave Horsfall
2024-04-05 2:07 ` Larry McVoy
2024-04-05 3:54 ` Greg 'groggy' Lehey
2024-04-05 4:03 ` G. Branden Robinson
2024-04-07 21:39 ` Dave Horsfall
2024-04-05 1:38 ` Noel Hunt [this message]
2024-04-05 10:11 ` Ralph Corderoy
2024-04-05 20:46 ` Noel Hunt
2024-04-05 6:48 ` Brad Spencer
2024-04-06 5:48 ` Kevin Bowling
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='CAGfO01zTgj1QtKCBpjUSxeYphVwf221tEqnMeS_CL4wZSif=Aw@mail.gmail.com' \
--to=noel.hunt@gmail.com \
--cc=TUHS@tuhs.org \
--cc=marcus.e.clark@outlook.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).