From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29872 invoked from network); 25 Nov 1998 09:26:13 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 25 Nov 1998 09:26:13 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id EAA28353; Wed, 25 Nov 1998 04:14:03 -0500 (EST) Resent-Date: Wed, 25 Nov 1998 04:14:03 -0500 (EST) Message-Id: <9811250857.AA08844@ibmth.df.unipi.it> To: Zsh Development Workers Subject: Re: FAQ bug In-Reply-To: "Phil Pennock"'s message of "Tue, 24 Nov 1998 19:15:29 NFT." <19981124191529.05649@athenaeum.demon.co.uk> Date: Wed, 25 Nov 1998 09:57:29 +0100 From: Peter Stephenson Resent-Message-ID: <"XbQp72.0.yw6.RfyMs"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4686 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Phil Pennock wrote: > In section 2.3 of the new FAQ, the first example of the zsh function for > cd is missing the closing double-quotes: > cd() { builtin cd "$@; echo $PWD; } yup, I've fixed that > As a thought: Bart pointed out $==* as an alternative to "$@" (one would > almost think he wanted to free up the syntax for something else :^) ... There was a problem pointed out by Zoli with $* which still applies to $==*, namely if you have cd as a function and want to do `cd foo ""' the null string gets dropped, and it means something completely different. There is now a mention of the difference between "$@" and $* in the shwordsplit section. I can point out about $==*, if you don't think it's going to make people's hair stand on end. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56100 Pisa, Italy