zsh-users
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: tlm@yoyo.cc.monash.edu.au
Cc: zsh-users@math.gatech.edu
Subject: Re: Zsh as /bin/sh on Linux?
Date: Fri, 19 Jan 1996 12:08:47 +0100 (MET)	[thread overview]
Message-ID: <199601191108.MAA10572@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199601190251.NAA05595@molly.cs.monash.edu.au> from "Tim Pickett" at Jan 19, 96 01:51:40 pm

Tim Pickett wrote:
> > Does anyone have any experience running zsh as /bin/sh on Linux?
> 
> My biggest problem with zsh is that it can often take quite a while to
> start up.  Granted, I have a pretty long .zshenv and even longer .zshrc,

It does not matter in this case.  When zsh is invoked as /bin/sh it will only
source the file in the ENV environment variable which really means that it
usually does not source anything since ENV is undefined.  Sourcing ENV is also
disabled if EUID != UID or EGID != GID.  Also zsh is faster than bash when
executing scripts.

Someone complaind that zsh is too big for /bin/sh.  This does not apply to
Linux since bash has about the same size az zsh (or even bigger).  Also if zsh
is the normal login shell of users it stays in the buffer cache.  Using
bash as /bin/sh means that bash should also stay in the buffers which consumes
more memory.  So in fact you may save some memory using the same shell in
/bin/sh as your login shell.

But really the biggest problem with zsh as sh is incompatibilities in variable
2substitution behaviour.  Probably most of these incompatibilities are bugs in
zsh.  I fixed the most important ones in my releases but I know that there are
still some differences.  Dispite these problems I used zsh as /bin/sh on my
home machine for several months without problems.  Now I use bash again but
only because I bought a new computer and reinstalled Linux on an empty
harddisk and I still did not changed sh to zsh.  Also my old machine had only
4 MB of RAM and it saved me a few Kbytes to use zsh as sh.  Now I have 16MB so
replacing bash with zsh is not so urgent now but I'll probably do that anyway
to catch the bugs.

Cheers,

Zoltan


      reply	other threads:[~1996-01-19 11:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-18 19:24 Steven L Baur
1996-01-18 20:18 ` Christopher White
1996-01-18 20:38   ` Jari Kokko
1996-01-18 20:41   ` Hrvoje Niksic
1996-01-18 21:22 ` Jeff "Obik" Epler
1996-01-18 21:45   ` Steven L Baur
1996-01-19 11:32   ` Zoltan Hidvegi
1996-01-19  2:51 ` Tim Pickett
1996-01-19 11:08   ` Zoltan Hidvegi [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=199601191108.MAA10572@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=tlm@yoyo.cc.monash.edu.au \
    --cc=zsh-users@math.gatech.edu \
    /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).