The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Noel Hunt <noel.hunt@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: TUHS@tuhs.org
Subject: [TUHS] Re: Does anyone have any memories of using cscope that they care to share?
Date: Sat, 6 Apr 2024 07:46:21 +1100	[thread overview]
Message-ID: <CAGfO01y7exVCSL5+n4tvWsnQOJBvSRbpZQEYT2X25kC1+FqhNA@mail.gmail.com> (raw)
In-Reply-To: <20240405101119.270161FA4D@orac.inputplus.co.uk>

'Samuel' is Rob Pike's 'sam' with some additions, those being the ability
to run 'cin' (C interpreter) on selected text, an 'advisor', which would
print the data type definition of selected text, and the 'browser', which
was an interface to cfront. Invoking 'browser' would fork a cscope
process running in line-oriented mode, and on button 3 were the
various search items that you will see in the normal cscope interface,
somewhat abbreviated. So you could select a piece of text, a name
of a function say, select 'calls to this function', and the results would
be added to the button 3 menu; selecting one of these takes you to
the file and line number in the cscope output.

There is one further addition, 'smudge'. It allows you to put a mark on
a place in a text file and assign an arbitrary name to it; these marks
then appear on a cascaded button 3 menu---select a mark, return to
that piece of text.

On Fri, Apr 5, 2024 at 9:11 PM Ralph Corderoy <ralph@inputplus.co.uk> wrote:
>
> Hi Noel,
>
> > And don't forget that 'samuel' had an interface to 'cscope'.
>
> I've used cscope.  What's samuel?
>
> --
> Cheers, Ralph.

  reply	other threads:[~2024-04-05 20:47 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
2024-04-05 10:11   ` Ralph Corderoy
2024-04-05 20:46     ` Noel Hunt [this message]
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=CAGfO01y7exVCSL5+n4tvWsnQOJBvSRbpZQEYT2X25kC1+FqhNA@mail.gmail.com \
    --to=noel.hunt@gmail.com \
    --cc=TUHS@tuhs.org \
    --cc=ralph@inputplus.co.uk \
    /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).