From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Marcus Clark <marcus.e.clark@outlook.com>, 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 10:35:13 +1100 [thread overview]
Message-ID: <Zg85MaFFx69SJMdW@hydra.lemis.com> (raw)
In-Reply-To: <20240404223828.GD2235@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Thursday, 4 April 2024 at 15:38:28 -0700, Larry McVoy wrote:
> On Thu, Apr 04, 2024 at 09:16:31PM +0000, Marcus Clark wrote:
>>
>> I wondered if anyone can add any interesting information about using
>> cscope on their projects or anything about its development.
>
> Interesting, no. Fond memories, absolutely. On SPARC machines with 4MB
> of ram, cscope was pretty essential if you wanted to get anything done.
> I used it a ton, made me way more productive.
Agreed. It was an essential tool when I was developing code. It just
seems funny to be asked about "memories" or "interesting". At an only
slightly different level, it would be like asking the same question
about, say, sh.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-04-04 23:35 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 [this message]
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
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=Zg85MaFFx69SJMdW@hydra.lemis.com \
--to=grog@lemis.com \
--cc=TUHS@tuhs.org \
--cc=lm@mcvoy.com \
--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).