From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8284 invoked from network); 15 Jan 1997 09:29:59 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 15 Jan 1997 09:29:59 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id EAA28847; Wed, 15 Jan 1997 04:36:06 -0500 (EST) Resent-Date: Wed, 15 Jan 1997 04:36:06 -0500 (EST) Message-Id: <199701150937.KAA00978@hydra.ifh.de> To: zsh-workers@math.gatech.edu (Zsh hackers list) Subject: #! problem Date: Wed, 15 Jan 1997 10:37:26 +0100 From: Peter Stephenson Resent-Message-ID: <"b4ku71.0.g27.5KAto"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2795 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Somebody here tried something like: #!/bin/zsh -f # ^^^^empty spaces added here echo your code here and got back: /bin/zsh: bad option: - This is a problem because, once again, previous versions of zsh weren't so fussy. (For comparison, ksh reacts similarly but you get `-f : bad option(s)' which is at least a little clearer.) This happens on IRIX, SunOS 4, AIX and Digital Unix 4.0, though apparently not on Solaris. I would think dropping meaningless spaces in an option string (i.e. when an option letter is expected) again would be harmless. I just want to wait for the waves of protest before trying anything. -- Peter Stephenson Tel: +49 33762 77366 WWW: http://www.ifh.de/~pws/ Fax: +49 33762 77413 Deutsches Elektronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen DESY-IfH, 15735 Zeuthen, Germany.