From: "Joshua Symons" <vmcore@mysun.com>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: Arthur Alinovi <aalinovi@panix.com>, zsh-users@sunsite.dk
Subject: Re: Why zsh?
Date: Sat, 31 Aug 2002 15:42:22 -0500 [thread overview]
Message-ID: <1c3d61cf3e.1cf3e1c3d6@mysun.com> (raw)
also good reading, posted this link (copy of original) because faqs.org
is down.
http://www.uni-giessen.de/faq/archiv/unix-faq.shell.shell-differences/msg00000.html
- Josh -
----- Original Message -----
From: "Bart Schaefer" <schaefer@brasslantern.com>
Date: Saturday, August 31, 2002 2:06 am
Subject: Re: Why zsh?
> On Aug 31, 1:43am, Arthur Alinovi wrote:
> }
> } So far, I'm very impressed by what I see. However, a friend of mine
> } (who is a bit of a unix wizard) uses tcsh and is curious as to what
> } zsh can do that tcsh couldn't do if he wrote a 500 line .cshrc file
>
> * Execute standard /bin/sh scripts.
>
> * Handle ANY signal, not just INT and HUP.
>
> * Redirect stderr without redirecting stdout as well.
>
> * Parse real semantic control structures (loops, functions, etc.)
> rather than syntactic sugar that sort of looks like a control
> structure. [%]
>
> And those are just the features common to any Bourne-like shell,
> such as
> bash or ksh as well as zsh. How about:
>
> * Do real multi-line editing of arbitrary text (not just command
> lines).
> * Do floating point arithmetic. (Ok, so you need zsh 4.x for that
> one.)
> * Save that 500 line startup file in byte-compiled form so it doesn't
> need to be parsed again the next time. (Yeah, that's 4.x as well.)
>
> I could go on, but there's no way to explain things like multios and
> process substitutions in two lines of text, and you should have the
> ideaby now.
>
> > "zsh is better that tcsh, because..."
>
> ... no one has yet had any reason to write a document entitled "Zsh
> Programming Considered Harmful."
>
> http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/
>
> ----------
> [%] I quote from <:"
> target="l">http://www.tcsh.org/tcsh.html/Control_flow.html>:
> "If the shell's input is not seekable, the shell buffers up input
> whenever a loop is being read and performs seeks in this internal
> buffer to accomplish the rereading implied by the loop."
>
> --
> Bart Schaefer Brass Lantern
> Enterpriseshttp://www.well.com/user/barts
> http://www.brasslantern.com
> Zsh: http://www.zsh.org | PHPerl Project:
> http://phperl.sourceforge.net
>
next reply other threads:[~2002-08-31 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 20:42 Joshua Symons [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-31 5:43 Arthur Alinovi
2002-08-31 7:06 ` Bart Schaefer
2002-09-01 16:39 ` William H. Magill
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=1c3d61cf3e.1cf3e1c3d6@mysun.com \
--to=vmcore@mysun.com \
--cc=aalinovi@panix.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/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).