zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@math.gatech.edu
Subject: Re: env variables
Date: 4 May 1998 03:39:45 GMT	[thread overview]
Message-ID: <slrn6kqe41.a1r.mason@coral.primenet.com.au> (raw)
In-Reply-To: <199805012044.NAA22048@wank.pdi.com>

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.
% csh -f
% set | fgrep "(" | cut -f1
argv
path
% env | egrep -i "^(argv|path)" | cut -f1 -d=
PATH

    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?

% set l=(a b "c d")
% foreach i ($l)
? echo $i
? end
a
b
c
d
% zsh -f
% l=(a b "c d")
% foreach i ($l); echo $i; end
a
b
c d

-- 
Geoff Wing   <gcw@pobox.com>            Mobile : 0412 162 441
Work URL: http://www.primenet.com.au/   Ego URL: http://pobox.com/~gcw/


  reply	other threads:[~1998-05-04  3:43 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 [this message]
1998-05-04 10:41           ` Bart Schaefer
1998-05-04 17:01           ` Nik Gervae
     [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=slrn6kqe41.a1r.mason@coral.primenet.com.au \
    --to=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).