Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Announcement draft
- X-seq: zsh-workers 1857
- From: bas@xxxxxxxxxxxx (Bas V. de Bakker)
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Announcement draft
- Date: 01 Aug 1996 08:36:50 +0200
- In-reply-to: Zoltan Hidvegi's message of Wed, 31 Jul 1996 23:11:12 +0200 (MET DST)
- References: <199607312111.XAA25395@xxxxxxxxxxxxxxxxx>
Zoltan Hidvegi <hzoli@xxxxxxxxxx> writes:
> More than a thousand bugs have been fixed since the release of
> zsh-2.5.0
This makes 2.5.0 sound quite unusable, which it wasn't. Are you also
counting the bugs introduced after 2.5.0?
> Additionally zsh is probably one of the most portable program
> available for Unix. It uses GNU autoconf and it builds out of the
> box on most systems.
Considering the amount of system calls a shell uses, it is surely very
portable. But I tend to doubt whether this is true when compared to
all kinds of programs that do not need to depend on system specific
features.
> /bin/sh can be safely linked to zsh.
This sounded too good to be true, so I just tested this on the perl
Configure script and it failed, sorry. (To be slightly more precise:
when typing '& -d' at a prompt to make it use the defaults zsh gives
me a parse error, while /bin/sh (POSIX, not traditional Bourne) has no
problems. This on HPUX 10.10.)
Bas.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author