The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Was curses ported to Seventh Edition Unix?
Date: Sat, 25 May 2024 10:28:32 -0500	[thread overview]
Message-ID: <20240525152832.zzjipv2wjcuedyld@illithid> (raw)
In-Reply-To: <ZlHCFj67W74P3v_p@largo.jsg.id.au> <CAKH6PiVnhwjuRZWxX-Gc0AU4fSaraNXUSPAnXX=taeSfVy6OyA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

Hi Jonathan & Doug,

At 2024-05-25T20:48:54+1000, Jonathan Gray wrote:
> On Fri, May 24, 2024 at 07:03:48PM -0500, G. Branden Robinson wrote:
> > 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?
> 
> "In particular, the C shell, curses, termcap, vi and
[ snip per Clem Cole ;-) ]
> were ported back to Version 7 (and later System III) so that it was
> not unusual to find these features on otherwise pure Bell releases."
> from Documentation/Books/Life_with_Unix_v2.pdf

Thanks!  This is exactly the sort of source citation I was looking for.

At 2024-05-25T11:06:24-0400, Douglas McIlroy wrote:
> Curses appears in the v8 manual but not v7. Of course a
> conclusion that it was not ported to v7 turns on dates.

I was confident that curses was not "part" of v7 because of these
factors.  (1) It wasn't in the manual; (2) archives of v7 in which we
now traffic as historical artifacts show no trace of it; and (3) the
story of its origin and development, even when distorted, doesn't place
it at the CSRC as far back as 1977/8.

But, if someone placed to know had claimed that it was, that would have
been a claim worth investigating.

> 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.

Perhaps one reason my question can be read two ways is that I'm
interested in both aspects of the issue.

I'm trying to write a "History" section for the primary ncurses man page
and clean up other problems its documentation has, like a boilerplate
reference to "Version 7 curses" in many of its other man pages, which
repeatedly implies such a thing as a separate line of development from
"BSD curses" and "System V curses".  I've been dubious of that language
since first encountering it, but I want a good documentary record to
support my proposal to chop it out.

> If curses was available when the v7 manual was prepared, I (who edited
> both editions) evidently was unaware of any dependence on it then.

I see no evidence that you missed it.  :)

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-05-25 15:28 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 ` [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   ` [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 [this message]
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=20240525152832.zzjipv2wjcuedyld@illithid \
    --to=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).