From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-7991-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 26075 invoked from network); 22 Sep 1999 01:24:45 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 22 Sep 1999 01:24:45 -0000
Received: (qmail 21518 invoked by alias); 22 Sep 1999 01:23:57 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 7991
Received: (qmail 21511 invoked from network); 22 Sep 1999 01:23:57 -0000
Date: Tue, 21 Sep 1999 18:23:51 -0700
From: Clint Olsen <olsenc@ichips.intel.com>
To: zsh-workers@sunsite.auc.dk
Subject: #!/path/to/arch-indep/zsh -f
Message-ID: <19990921182350.A45626@ichips.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
Organization: Intel Corporation, Hillsboro, OR
X-Disclaimer: Mutt Bites!

Hello:

FYI, I'm using zsh-3.1.6.

I decided to change my script to reflect the copy of my shell, and attempt
to direct it to the path of my zsh wrapper itself causes the script to
misfire when it is executed from *csh.  I've narrowed it down to a machine
independent wrapper I have which seems to be hampering starting the
interpreter.  It is:

#!/bin/sh

if [ -f $OTOOLS/bin/$OS/zsh ]; then
  exec $OTOOLS/bin/$OS/zsh $*
else
  exec /usr/intel/bin/zsh $*
fi

Is this the most robust way to handle this?

-Clint