zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Raъl Nъсez de Arenas Coronado" <dervishd@jazzfree.com>,
	zsh-workers@sunsite.dk
Subject: RE: About ZSH vs. BASH
Date: Wed, 4 Jul 2001 18:57:32 +0400	[thread overview]
Message-ID: <002c01c10499$a743f280$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <E15HX38-000022-00@DervishD>

>
>     So, the choice is quite simple: we will take zsh as our system
> shell and sometime in the future, if necessary, will start our shell
> project (if possible...). The problem here is that we use to compile
> the programs we run, because our directory layout is special and
> because our Linux is hand-made, not a distribution. So, we need a
> shell capable of interpret the './configure' scripts and other
> scripts which came with the sources.
>
>     At this point we fully know that BASH interprets them, and we
> want to know if we can use zsh not only as an user shell, but if we
> can use it as our /bin/sh, fully replacing BASH; the problem is
> precisely this: we cannot use both shells, although we could consider
> using zsh & ash. This is not sure at all, so we would sleep better if
> zsh could be used as a full replacement.
>

This should be possible. zsh is not fully bash-compatible, but it should be
to the large extent sh-compatible (where sh means POSIX sh) if called as sh.
I just run zsh's own configure with zsh in shell mode.

But we do not have any specific compatibility tests. Keep in mind that many
Linux scripts silently assume bash and are *not* portable. It is not zsh
fault :-)

-andrej


      reply	other threads:[~2001-07-04 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 20:45 Raúl Núñez de Arenas Coronado
2001-07-04 14:57 ` Andrej Borsenkow [this message]

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='002c01c10499$a743f280$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=dervishd@jazzfree.com \
    --cc=zsh-workers@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).