From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: bash conversion trouble.
Date: Sun, 26 Feb 2017 10:03:38 -0800 [thread overview]
Message-ID: <70cf4e82-ff54-8a7a-17a6-993d841a98dc@eastlink.ca> (raw)
In-Reply-To: <170226091941.ZM14996@torch.brasslantern.com>
On 26/02/17 09:19 AM, Bart Schaefer wrote:
> The goals were not at all similar. Bash was an effort to re-create the
> Bourne shell under the GPL; zsh was an effort to introduce structured
> shell language and scripting to csh users.
Most interesting. An insight like that will explain much. I presumed
bash to be no more than the natural evolution of sh and zsh to be more
or less the same, with no particular nod to csh. I know that ksh was a
truly separate project. Is there a brief history of shells that one
might read? Anyway, I always took differences between zsh and bash to
be 'deliberate' if that's the right word -- gorillas making a very
definite point of not being orange. Thus my original question and now I
see what you were getting at as far as gorillas.
next prev parent reply other threads:[~2017-02-26 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 1:35 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 [this message]
2017-02-26 21:10 ` Shell history (Re: bash conversion trouble.) Bart Schaefer
2017-02-26 23:23 ` 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=70cf4e82-ff54-8a7a-17a6-993d841a98dc@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).