From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20495 invoked from network); 4 May 1998 17:11:14 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 4 May 1998 17:11:14 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id NAA29971; Mon, 4 May 1998 13:05:59 -0400 (EDT) Resent-Date: Mon, 4 May 1998 13:05:59 -0400 (EDT) Date: Mon, 4 May 1998 10:01:28 -0700 Message-Id: <199805041701.KAA29016@wank.pdi.com> MIME-Version: 1.0 From: Nik Gervae To: mason@primenet.com.au Cc: zsh-workers@math.gatech.edu Subject: Re: env variables Newsgroups: lists.zsh.workers In-Reply-To: References: <199805012044.NAA22048@wank.pdi.com> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Reply-To: Nik Gervae Content-Type: text/plain; charset=US-ASCII Resent-Message-ID: <"zgVjw1.0.AK7.sLVJr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3924 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Geoff Wing writes: > Nik Gervae typed: > :> Arrays aren't exported, because there's no standard or de facto method of > :> exporting arrays, so nothing would understands them. Only strings are > :> exported. From your example, CDPATH is a string, cdpath is an array. > :Hmm. That sounds slightly fishy in that csh happily exports array > :variables, but then csh is bogus in so many ways.... I've managed > > Not as arrays. In fact, I can't see it doing it at all. > [...] > but PATH is a colon separated string. path is a space separated string > which is pretending to be an array. You could export it as such but it > would be useless. What happens when an element in the array has a space > in it? That's exactly right. csh happily exports the variable as it would print its contents, minus the parentheses. At this point I'm more inclined to think that the program that's getting such an environment variable is making a serious mistake than to think that zsh is defective. --Nik