From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Was curses ported to Seventh Edition Unix?
Date: Sat, 25 May 2024 11:06:24 -0400 [thread overview]
Message-ID: <CAKH6PiVnhwjuRZWxX-Gc0AU4fSaraNXUSPAnXX=taeSfVy6OyA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
> 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?
Curses appears in the v8 manual but not v7. Of course a
conclusion that it was not ported to v7 turns on dates. Does
v7 refer to a point in time or an interval that extended until we
undertook to prepare the v8 manual? Obviously curses was
ported during or before that interval. If curses was available
when the v7 manual was prepared, I (who edited both editions)
evidently was unaware of any dependence on it then.
Doug
[-- Attachment #2: Type: text/html, Size: 749 bytes --]
next prev reply other threads:[~2024-05-25 15:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 0:03 G. Branden Robinson
2024-05-25 0:46 ` [TUHS] " Clem Cole
2024-05-25 0:57 ` 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 ` Douglas McIlroy [this message]
2024-05-25 15:11 ` 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
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='CAKH6PiVnhwjuRZWxX-Gc0AU4fSaraNXUSPAnXX=taeSfVy6OyA@mail.gmail.com' \
--to=douglas.mcilroy@dartmouth.edu \
--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).