zsh-users
 help / color / mirror / code / Atom feed
From: Bernd Eggink <eggink@rrz.uni-hamburg.de>
To: Andrew Main <zefram@tao.co.uk>
Cc: adam.spiers@new.ox.ac.uk, zsh-users@math.gatech.edu
Subject: Re: Exporting arrays
Date: Mon, 12 Jan 1998 14:48:45 +0100	[thread overview]
Message-ID: <34BA1F3D.18EE4BAB@rrz.uni-hamburg.de> (raw)
In-Reply-To: <199801121045.KAA05850@taos.demon.co.uk>

Andrew Main wrote:

[ snip ]

> Btw, it's impossible to export an array.  Unix environment variables are
> only strings.  There are ways an array could be encoded as a string,
> but some other shells get very unhappy about apparently malformed
> environment entries.
> 
> -zefram

As a workaround, you could convert the array into a word list, using a
suited delimiter:

   a=(one two three four)
   export aex=${(j(:))a}

Then, in the subshell, convert the list back into an array:

   a=(${(s(:))aex})

Unfortunately this doesn't work if an array element is empty! Example:

   a=(one '' three four)
   export aex=${(j(:))a}   # aex=one::three:four
   # ...
   a=(${(s(:))aex})        # a=(one three four), $#a == 3

I reported this (IMHO) bug already some weeks ago. Has anybody tried to
fix it? I wasn't able yet to localize it in the sources.

	Bernd
   



--
Bernd Eggink
Regionales Rechenzentrum der Uni Hamburg
eggink@rrz.uni-hamburg.de
http://www.rrz.uni-hamburg.de/eggink/BEggink.html


  reply	other threads:[~1998-01-12 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-11 18:16 Adam Spiers
1998-01-12  3:51 ` Geoff Wing
1998-01-12  9:01 ` Peter Stephenson
1998-01-12 10:45 ` Andrew Main
1998-01-12 13:48   ` Bernd Eggink [this message]
1998-01-12 15:15     ` Andrew Main
1998-01-12 21:24       ` Bernd Eggink
1998-01-12 22:12       ` Adam Spiers
1998-01-12 23:15         ` Mirar
1998-01-13  1:39           ` Adam Spiers
1998-01-13 14:12             ` Mirar

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=34BA1F3D.18EE4BAB@rrz.uni-hamburg.de \
    --to=eggink@rrz.uni-hamburg.de \
    --cc=adam.spiers@new.ox.ac.uk \
    --cc=zefram@tao.co.uk \
    --cc=zsh-users@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).