zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: exported unset variables [was: 'export -p' lacks POSIX output]
Date: Sat, 29 Oct 2016 19:43:08 +0100	[thread overview]
Message-ID: <20161029194308.32b96bca@ntlworld.com> (raw)
In-Reply-To: <161029110904.ZM2918@torch.brasslantern.com>

On Sat, 29 Oct 2016 11:09:04 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> That one potentially gets rather ugly; consider:
> 
> % setopt POSIXBUILTINS
> % export var
> % var=()
> zsh: var: attempt to assign array value to non-array
> 
> Is that OK with everyone?

We've generally taken the attitude that POSIX copmliance settings aren't
intended to be useful to native zsh users, just compatible for everyone
else, so what it used to do isn't a big issue.  I think this fits in
that category.

I don't think exporting arrays would be that hard, but if you want to do
it, the right way is probably to use "typeset -T" and specify which
character you want the elements to be joined with.

pws


  reply	other threads:[~2016-10-29 18:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22  3:02 'export -p' lacks POSIX output Martijn Dekker
2016-10-22 18:24 ` Bart Schaefer
2016-10-23 12:00   ` Martijn Dekker
2016-10-23 16:47     ` Bart Schaefer
2016-10-24  8:33   ` Peter Stephenson
2016-10-28 21:00 ` exported unset variables [was: 'export -p' lacks POSIX output] Martijn Dekker
2016-10-28 21:31   ` Bart Schaefer
2016-10-28 21:48     ` Martijn Dekker
2016-10-29  0:18       ` Bart Schaefer
2016-10-29  8:11         ` Martijn Dekker
2016-10-29 18:09           ` Bart Schaefer
2016-10-29 18:43             ` Peter Stephenson [this message]
2016-10-29 19:05           ` Bart Schaefer
2016-10-29 20:20             ` interactive comments [was: exported unset variables] Martijn Dekker
2016-10-30  1:25               ` Bart Schaefer

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=20161029194308.32b96bca@ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /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).