From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26773 invoked by alias); 3 Jun 2010 15:11:44 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 27997 Received: (qmail 8593 invoked from network); 3 Jun 2010 15:11:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at csr.com does not designate permitted sender hosts) Date: Thu, 3 Jun 2010 15:20:55 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Cc: Martin Buchholz , Joel Ebel Subject: Re: zsh ignores the arguments on its first command. Message-ID: <20100603152055.70332aec@csr.com> In-Reply-To: References: <201006012145.o51LjhGg005724@pws-pc.ntlworld.com> <20100602121901.6ce71329@csr.com> <20100603100109.1b090b4e@csr.com> <20100603143220.48ccbf3e@csr.com> Organization: Cambridge Silicon Radio X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.9; i686-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jun 2010 14:20:55.0487 (UTC) FILETIME=[FAB38CF0:01CB0327] X-Scanned-By: MailControl A_09_40_00 (www.mailcontrol.com) on 10.68.1.161 On Thu, 3 Jun 2010 07:15:59 -0700 Bart Schaefer wrote: > Martin has something of a point in that when getparamnode() calls > zerr() for this, the shell behaves somewhat as if ${terminfo?} had > been used rather than ${+terminfo}. > > Perhaps the correct thing here is to change this to a zwarn() and > allow the setting of the UNSET option to control whether autoload > failure aborts the script. I'm not convinced that's right, either, > though. Yes, as you'll see from the comment just above the code I changed, I had upgraded it from a warning to an error, since it doesn't mean "the shell programmer didn't get around to setting this variable" it means "something nasty happened such that this variable that you were expecting to implement special behaviour is never going to do what you expect". I think that's a hard(er) error. -- Peter Stephenson Software Engineer Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom