From: Martijn Dekker <martijn@inlv.org>
To: Bart Schaefer <schaefer@brasslantern.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: exported unset variables [was: 'export -p' lacks POSIX output]
Date: Fri, 28 Oct 2016 22:48:57 +0100 [thread overview]
Message-ID: <bec1e0c3-ad4a-6513-726e-049723d18c24@inlv.org> (raw)
In-Reply-To: <161028143156.ZM19947@torch.brasslantern.com>
Op 28-10-16 om 22:31 schreef Bart Schaefer:
> On Oct 28, 10:00pm, Martijn Dekker wrote:
> }
> } In zsh, however, variables are automatically set to the empty value upon
> } being exported.
>
> That's no longer true subsequent to my "export -p" patch:
>
> torch% export XYZPDQ
> torch% export -p | grep XYZPDQ
> export XYZPDQ
> torch% printenv | grep XYZPDQ
> torch%
>
> Unless there's some other nuance here that I'm missing?
Hmm... With current git version:
$ PS1='%% ' Src/zsh -f -o posixbuiltins
% unset -v var
% export var
% echo ${var+s} # this shows it as set (should be unset)
s
% export -p var # but this shows it as unset
export var
% var=''
% export -p var # 'export' knows if it's set or not, ${var+s} doesn't?
export var=''
So, currently, ${var+s} doesn't correctly represent that an exported
'var' is unset.
(Also, is it correct/expected behaviour that zsh doesn't parse comments
on the interactive command line? Blindly copying/pasting the above won't
work for that reason.)
Thanks,
- M.
next prev parent reply other threads:[~2016-10-28 21:49 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 [this message]
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
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=bec1e0c3-ad4a-6513-726e-049723d18c24@inlv.org \
--to=martijn@inlv.org \
--cc=schaefer@brasslantern.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).