The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Origin year of BSD csh?
Date: Tue, 28 Jun 2016 01:51:44 -0600	[thread overview]
Message-ID: <201606280751.u5S7piO2014270@freefriends.org> (raw)
In-Reply-To: <20160628064935.GF83438@server.rulingia.com>

Thanks everyone for the answers, esp. to Mary Ann for the definitive dates.

My story is similar to most everyone else's. I was exposed to csh on
4.1 BSD but was so horrified by the syntax that I preferred to do without
job control and use the Bourne shell.

Later on when I was at Georgia Tech we got the BRL dist and I used Ron's
job control shell. I wrote a csh-style history mechanism for it and backported
that and the job control to the V7 sh and posted diffs to USENET so that people
without a SV license could benefit.

From there I went to ksh for many years, and thence to Bash. I abandoned
the csh-history-for-sh stuff as soon as I got ksh with vi editing mode
and have never looked back.  Circa 1990 I banged on the bash/readline code
to make its vi mode more like ksh's.

How well I remember Bournegol and how happy I was when I saw that SVR2 had
gotten rid of it.

With respect to history in the terminal, the Bell Labs guys did that by
making the terminal smarter, with the Blit.  I had one but the load it
put on our poor vax 11/780 was awesome.

Arnold


  reply	other threads:[~2016-06-28  7:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 10:14 Aharon Robbins
2016-06-26 16:30 ` Mary Ann Horton
2016-06-26 18:14   ` Larry McVoy
2016-06-26 18:32     ` Ronald Natalie
2016-06-26 20:43       ` John Cowan
2016-06-27  0:59         ` Larry McVoy
2016-06-27  1:11           ` John Cowan
2016-06-27 11:27       ` Sven Mascheck
2016-06-27 12:47         ` Steve Nickolas
2016-06-27 14:58         ` Joerg Schilling
2016-06-27 15:29           ` Ronald Natalie
2016-06-27 16:22         ` John Cowan
2016-06-27 16:35           ` Steve Nickolas
2016-06-27 20:00         ` Dave Horsfall
2016-06-27 20:33         ` Ronald Natalie
2016-06-27 20:44           ` Clem Cole
2016-06-27 21:02           ` Steve Nickolas
2016-06-27 21:15             ` Ronald Natalie
2016-06-27 21:20           ` John Cowan
2016-06-27 21:28             ` Ronald Natalie
2016-06-27 21:45               ` John Cowan
2016-06-28  6:49               ` Peter Jeremy
2016-06-28  7:51                 ` arnold [this message]
2016-06-27 21:29           ` Random832
2016-06-28 14:47         ` Tony Finch
2016-06-26 19:41     ` Clem Cole
2016-06-27 10:31       ` Joerg Schilling
2016-06-27 13:01         ` Ronald Natalie
2016-06-27 13:15           ` Steffen Nurpmeso
2016-06-27 15:17           ` Joerg Schilling
2016-06-27 13:39         ` [TUHS] Bizarre job control, was csh Warren Toomey
2016-06-27 15:00           ` Steve Nickolas
2016-06-27 15:13             ` Joerg Schilling
2016-06-27 15:23               ` Steve Nickolas
2016-06-26 20:58     ` [TUHS] Origin year of BSD csh? Steve Nickolas
2016-06-27 10:03 ` Joerg Schilling

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=201606280751.u5S7piO2014270@freefriends.org \
    --to=arnold@skeeve.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).