zsh-workers
 help / color / mirror / code / Atom feed
From: Nik Gervae <Nik@pdi.com>
To: mason@primenet.com.au
Cc: zsh-workers@math.gatech.edu
Subject: Re: env variables
Date: Mon, 4 May 1998 10:01:28 -0700	[thread overview]
Message-ID: <199805041701.KAA29016@wank.pdi.com> (raw)
In-Reply-To: <slrn6kqe41.a1r.mason@coral.primenet.com.au>

Geoff Wing writes:
> Nik Gervae <Nik@pdi.com> 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


  parent reply	other threads:[~1998-05-04 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-30 20:56 Timothy Doyle
1998-04-30 23:01 ` Nik Gervae
1998-05-01  5:22 ` Geoff Wing
1998-05-01 17:21   ` Nik Gervae
1998-05-01 19:47     ` Geoff Wing
1998-05-01 20:44       ` Nik Gervae
1998-05-04  3:39         ` Geoff Wing
1998-05-04 10:41           ` Bart Schaefer
1998-05-04 17:01           ` Nik Gervae [this message]
     [not found]       ` <74885733@toto.iv>
1998-05-05  0:52         ` Nik Gervae

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199805041701.KAA29016@wank.pdi.com \
    --to=nik@pdi.com \
    --cc=mason@primenet.com.au \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).