The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Origin of the BSD csh?
       [not found] <mailman.13.1466989190.30583.tuhs@minnie.tuhs.org>
@ 2016-06-27 14:10 ` David
  0 siblings, 0 replies; only message in thread
From: David @ 2016-06-27 14:10 UTC (permalink / raw)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]


> On Jun 26, 2016, at 5:59 PM, tuhs-request at minnie.tuhs.org wrote:
> 
> I detested the CSH syntax.   In order to beat back the CSH proponents at BRL, I added JOB control to the SV  (and later SVR2) Bourne Shell.   Then they beat on me for not having command like editing in (a la TCSH), so I added that.   This shell went out as /bin/sh in the Doug Gwyn SV-on-BSD release so every once and a while over the years I trip across a “Ron shell” usually people who were running Mach-derived things that ran my shell as /bin/sh. 

When porting BSD to new hardware at Celerity (later Floating Point, now part of Sun, oops Oracle) I got ahold of the code that Doug was working on and made the jsh (Job control sh) my shell of choice. Now that Bash does all of those things and almost everything emacs can do, Bash is my shell.

As far as customizing, I’ve got a .cshrc that does nothing more than redirect to a launch of bash if available and /bin/sh if nothing else. And my scripts for logging in are so long a convoluted due to many years of various hardware and software idiosyncratic changes (DG/UX anyone, anyone?) that I’m sure most of it is now useless. And I don’t change it for fear of breaking something.

	David



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-06-27 14:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.13.1466989190.30583.tuhs@minnie.tuhs.org>
2016-06-27 14:10 ` [TUHS] Origin of the BSD csh? David

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