From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Origin year of BSD csh?
Date: Tue, 28 Jun 2016 06:00:03 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1606280555430.1057@aneurin.horsfall.org> (raw)
In-Reply-To: <20160627112732.GA8110@autechre4>
On Mon, 27 Jun 2016, Sven Mascheck wrote:
> I've always been intrigued by the fact that traditional Bourne shell and
> Almquist shell haven't implemented history or command line editing.
I hated CSH, and only used it when forced to; I used a utility called
"screen" for my job-switching needs, and was really happy when KSH came
along (then ZSH).
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-06-27 20:00 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 [this message]
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
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=alpine.BSF.2.11.1606280555430.1057@aneurin.horsfall.org \
--to=dave@horsfall.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).