zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Shell history (Re: bash conversion trouble.)
Date: Sun, 26 Feb 2017 13:10:40 -0800	[thread overview]
Message-ID: <170226131040.ZM4640@torch.brasslantern.com> (raw)
In-Reply-To: <70cf4e82-ff54-8a7a-17a6-993d841a98dc@eastlink.ca>

On Feb 26, 10:03am, Ray Andrews wrote:
}
} Is there a brief history of shells that one might read?

This:

http://www.softpanorama.org/People/Shell_giants/introduction.shtml

has the timeline mostly correct; but the author is so far off on the
relative merits of the Bourne and C shell scripting languages, for
example, as to make most of his editorializing ignorable.  He seems
to have some kind of axe to grind with Steve Bourne and wastes a lot
of words bashing him (no pun intended), but there is a lot of useful
source material quoted or linked.

(As an example, the Bourne language can be sensibly pre-parsed into an
execution tree -- the basis for zsh's eventual adoption of wordcode for
internal representation -- whereas the csh language makes no sense if
it is not executed in parallel with parsing.  I've even written self-
modifying csh programs that take advantage of this by overwriting the
tail of their own input file in the middle of a loop.)

This:

http://www.ibm.com/developerworks/library/l-linux-shells/

has a chart showing the timeline in detail, though to put zsh on a
direct line from csh is also misleading; it was written from scratch
and should probably have dotted lines from all of csh, ksh, and rc
as ideas were borrowed from all of those (the ksh ideas having been
taken from a [sometimes mis-] reading of the ksh manual pages, as
ksh implementations were still proprietary at that time).

Several of the O'Reilly Media books on shell programming also contain
chapters on shell history, which are accurate to varying degrees though
more correct than not.


  reply	other threads:[~2017-02-26 21:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25  1:35 bash conversion trouble Ray Andrews
2017-02-25  4:41 ` Bart Schaefer
2017-02-25 15:13   ` Ray Andrews
2017-02-25 15:26     ` Peter Stephenson
2017-02-25 15:55       ` Bart Schaefer
2017-02-25 16:24         ` Ray Andrews
2017-02-25 17:02           ` Bart Schaefer
2017-02-25 19:13             ` Ray Andrews
2017-02-25 20:09               ` Bart Schaefer
2017-02-26  5:05                 ` Ray Andrews
2017-02-26 17:19                   ` Bart Schaefer
2017-02-26 18:03                     ` Ray Andrews
2017-02-26 21:10                       ` Bart Schaefer [this message]
2017-02-26 23:23                         ` Shell history (Re: bash conversion trouble.) Ray Andrews
2017-02-28 15:56             ` bash conversion trouble Stephane Chazelas
2017-02-28 19:27               ` Ray Andrews

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=170226131040.ZM4640@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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