From: Clem Cole <clemc@ccc.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Was curses ported to Seventh Edition Unix?
Date: Fri, 24 May 2024 20:46:19 -0400 [thread overview]
Message-ID: <CAC20D2O8svnQypQcf6j_6jtx+aTyYSeJ9TRySo7xw1Be6+c9=A@mail.gmail.com> (raw)
In-Reply-To: <20240525000348.hq5zvwm6x4evl44h@illithid>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
I’m traveling this weekend so I’m doing this by memory. ISTR The original
curses was developed on Ing70 as part of Rogue and that It missed the 2BSD
tape by about a year. See if you can find an early Rogue distribution and
I think you’ll find it there. If not look in the early net news source
distributions.
Sent from a handheld expect more typos than usual
On Fri, May 24, 2024 at 8:04 PM G. Branden Robinson <
g.branden.robinson@gmail.com> wrote:
> Hi folks,
>
> I'm finding it difficult to find any direct sources on the question in
> the subject line.
>
> Does anyone here have any source material they can point me to
> documenting the existence of a port of BSD curses to Unix Version 7?
>
> I know that curses made it into 2.9BSD for the PDP-11, but that's not
> quite the same thing.
>
> There are comments in System V Release 2's curses.h file[1][2] (very
> different from 4BSD's[3]) that suggest some effort to accommodate
> Version 7's terminal driver. So I would _presume_ that curses got
> ported to Version 7. But that's System V, right when it started
> diverging from BSD curses, and moreover, presumption is not evidence.
>
> Even personal accounts/anecdotes would be helpful. Maybe some of you
> _wrote_ curses applications for Version 7 machines.
>
> Regards,
> Branden
>
> [1] System III apparently did not have curses at all. Both it and 4BSD
> were released in 1980. System V Release 1 doesn't seem to, either.
> [2]
> https://github.com/ryanwoodsmall/oldsysv/blob/master/sysvr2-vax/include/curses.h
> [3]
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=4BSD/usr/include/curses.h
>
[-- Attachment #2: Type: text/html, Size: 2412 bytes --]
next prev parent reply other threads:[~2024-05-25 0:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 0:03 [TUHS] " G. Branden Robinson
2024-05-25 0:46 ` Clem Cole [this message]
2024-05-25 0:57 ` [TUHS] " G. Branden Robinson
2024-05-25 10:48 ` Jonathan Gray
2024-05-25 11:08 ` Arrigo Triulzi via TUHS
2024-05-25 12:16 ` Clem Cole
2024-05-25 23:06 ` Rob Pike
2024-05-25 15:06 ` [TUHS] " Douglas McIlroy
2024-05-25 15:11 ` [TUHS] " Rich Salz
2024-05-25 15:40 ` Clem Cole
2024-05-25 15:43 ` Clem Cole
2024-05-25 15:51 ` Clem Cole
2024-05-25 15:57 ` G. Branden Robinson
2024-05-25 16:06 ` Clem Cole
2024-05-25 16:13 ` G. Branden Robinson
2024-05-25 16:21 ` Clem Cole
2024-05-25 16:38 ` G. Branden Robinson
2024-05-25 17:02 ` Warner Losh
2024-05-25 16:14 ` Clem Cole
2024-05-25 16:25 ` G. Branden Robinson
2024-05-25 18:07 ` Adam Sampson
2024-05-27 18:31 ` Mary Ann Horton
2024-05-25 15:28 ` G. Branden Robinson
2024-05-25 17:24 Steve Simon
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='CAC20D2O8svnQypQcf6j_6jtx+aTyYSeJ9TRySo7xw1Be6+c9=A@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=g.branden.robinson@gmail.com \
--cc=tuhs@tuhs.org \
/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).