From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8600 invoked from network); 22 Sep 1999 09:24:11 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Sep 1999 09:24:11 -0000 Received: (qmail 16328 invoked by alias); 22 Sep 1999 09:24:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7996 Received: (qmail 16305 invoked from network); 22 Sep 1999 09:23:56 -0000 From: "Bart Schaefer" Message-Id: <990922091316.ZM16279@candle.brasslantern.com> Date: Wed, 22 Sep 1999 09:13:16 +0000 In-Reply-To: <19990921182350.A45626@ichips.intel.com> Comments: In reply to Clint Olsen "#!/path/to/arch-indep/zsh -f" (Sep 21, 6:23pm) References: <19990921182350.A45626@ichips.intel.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Clint Olsen , zsh-workers@sunsite.auc.dk Subject: Re: #!/path/to/arch-indep/zsh -f MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 21, 6:23pm, Clint Olsen wrote: } Subject: #!/path/to/arch-indep/zsh -f } } 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. And the error you get is something like "exec format error", I suppose. Most (I don't know if I can say "all") operating systems won't do two levels of indirection via #! lines. That is, if the thing on the #! line is not itself a binary in executable format, the OS will not recognize yet another #! line and launch still another interpreter. The workaround is to write your wrapper in C and compile it. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com