From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24798 invoked from network); 19 Sep 2002 16:06:55 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Sep 2002 16:06:55 -0000 Received: (qmail 25442 invoked by alias); 19 Sep 2002 16:06:49 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17710 Received: (qmail 25430 invoked from network); 19 Sep 2002 16:06:48 -0000 Date: Thu, 19 Sep 2002 18:15:32 +0200 From: DervishD To: Peter Stephenson Cc: David =?iso-8859-1?Q?G=F3mez?= , Zsh hackers list Subject: Re: Using zsh in gcc compilation Message-ID: <20020919161532.GA4811@DervishD> References: <20020919150720.GA14948@fargo> <16798.1032448732@csr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16798.1032448732@csr.com> User-Agent: Mutt/1.4i Organization: Pleyades Net Sender: =?iso-8859-1?B?UmH6bCBO+vFl?= =?iso-8859-1?Q?z?= de Arenas Coronado Hi Peter (and David) :) > > $options variable to store the first positional parameter to > That's extremely plausible --- `on' occurs very frequently in $options. > But that implies the zsh/parameter module is loaded. I've tested and even invoking an interactive '/bin/sh' (hardlinked to /bin/zsh) doesn't define $options... It's very strange that David' Zsh does this :? > It's a shame we didn't initially use names like zsh_options instead. Well, a namespace like that can be added progresively, substituting over time the actual one without breaking current configuration (I hope). Raśl