From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Origin year of BSD csh?
Date: Sun, 26 Jun 2016 16:58:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1606261654030.76251@frieza.hoshinet.org> (raw)
In-Reply-To: <20160626181450.GK26734@mcvoy.com>
On Sun, 26 Jun 2016, Larry McVoy wrote:
> On Sun, Jun 26, 2016 at 09:30:39AM -0700, Mary Ann Horton wrote:
>> I brought csh with me to Bell Labs in the summer of 1979. The folks at Bell
>> Labs recoiled in horror: they had just gone through a painful conversion
>> from the Mashey shell to the Bourne shell
>
> I used csh for a while before ksh became available. It was an improvement
> over the Bourne shell, IMO, but once ksh came out I went back to Bourne
> shell syntax. And now bash is pretty nice.
>
> --lm
For some daft reason my first foray onto the Unix command line was tcsh,
and later I switched to bash, which is still my primary choice - though I
don't mind using any other Korn-type shell, long as I got my "emacs
editing" mode (although the real ksh's tab completion is clunkier than
bash's).
Using a Bourne shell that doesn't have a line editor is a pain in the
keester, but if I must, I can deal.
I have no idea how to use csh, and if I'm set up with csh as my default
shell the first thing I'll do is try to switch it to bash or ksh!
-uso.
next prev parent reply other threads:[~2016-06-26 20:58 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
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 ` Steve Nickolas [this message]
2016-06-27 10:03 ` [TUHS] Origin year of BSD csh? 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.02.1606261654030.76251@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).