The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Origin year of BSD csh?
Date: Mon, 27 Jun 2016 17:02:58 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.02.1606271700300.65884@frieza.hoshinet.org> (raw)
In-Reply-To: <E4DCAA3E-77BA-43C3-806E-19657EF23E36@ronnatalie.com>

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

On Mon, 27 Jun 2016, Ronald Natalie wrote:

>
>> On Jun 27, 2016, at 6:27 AM, Sven Mascheck <mascheck at in-ulm.de> wrote:
>>
>> On Sun, Jun 26, 2016 at 01:32:23PM -0500, Ronald Natalie wrote:
>>> 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.
>>
>> How interesting, I will try to bother you (perhaps directly) about
>> in-depth informations :-)
>>
>
> Sure, it was a long time ago, but I’ll tell you what I remember.  The 
> one thing I do remember is that the SV /bin/sh was written in these 
> horrendous macros that sort of made it look like algol or something.

That was inherited from the original V7 Bourne shell.  And "horrendous" 
doesn't even begin to describe that disaster of coding.

> When the SVR2 shell came out, someone (not Bourne obviously) had undone 
> all those in favor of the native C++ if/else/while blocking.
>>
>> I've always been intrigued by the fact that traditional Bourne shell and
>> Almquist shell haven't implemented history or command line editing.
>
> Command line editing might have been implemented in the driver as 
> enhanced editing in “cooked” mode, but the history is a bit more context 
> specific.

I kind-of like the MS-DOS 5 approach of having a separate tool that the 
shell can optionally link to that provides those capabilities.

*ducks and runs*

-uso.


  parent reply	other threads:[~2016-06-27 21:02 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 [this message]
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.02.1606271700300.65884@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).