From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14302 invoked from network); 5 Jun 2001 15:52:51 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Jun 2001 15:52:51 -0000 Received: (qmail 13386 invoked by alias); 5 Jun 2001 15:52:31 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14723 Received: (qmail 13375 invoked from network); 5 Jun 2001 15:52:30 -0000 Message-ID: <20010605155236.50747.qmail@web12508.mail.yahoo.com> Date: Tue, 5 Jun 2001 08:52:36 -0700 (PDT) From: a normal guy Subject: Re: Export problem To: Zsh Hackers In-Reply-To: <1010605064402.ZM4270@candle.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Bart Schaefer wrote: > On Jun 5, 9:18am, Andrej Borsenkow wrote: > } Subject: RE: Export problem > } > } This is a bug. No field splitting should be done in > parameter assignment > } context. > > The arguments of the `export' command are not a parameter > assignment context, > or at least zsh has never treated them as such. If you want > parameter > assignment context, you have to do two separate commands: > > RUN_DATE=`date +%Y%m%e%H%M.%S` > export RUN_DATE > > This does not do field splitting. > > If the SUS says elsewhere that the arguments of `export' (and > `typeset' et al.) are to be parsed as parameter assignments, > we're going to have to change `export' (etc.) from command > names to keywords. As for compatibility with other shells (POSIX, Korn shell, BASH), this would need to be addressed. An option setting would do if necessary. Scott __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/