From: Martijn Dekker <martijn@inlv.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 'export -p' lacks POSIX output
Date: Sun, 23 Oct 2016 14:00:42 +0200 [thread overview]
Message-ID: <2047d07f-c5c1-6b8f-3d2d-cfcc2c06b875@inlv.org> (raw)
In-Reply-To: <161022112423.ZM6178@torch.brasslantern.com>
Op 22-10-16 om 20:24 schreef Bart Schaefer:
> Would anyone object if this just happened all the time, rather than
> depending on POSIXBUILTINS + "export"?
After the patch, variables with a non-scalar type get output such as:
export -i10 SHLVL=2
Option flags to 'export' other than -p are not POSIX, and POSIX
specifies output without any flags for 'export -p'.
Maybe that implies that commands like 'export -p' and 'trap' should
generate commands suitable for any POSIX shell. This would mean the
$'...' quoting method should also be deactivated. It may become POSIX at
some point, but it's anyone's guess how long that will take, and then
shells have to implement it. Then again, POSIX says the input should be
"suitable for reinput to the shell", not "suitable for reinput to any
POSIX shell".[*]
In any case, if the output needs to be conditional upon POSIXBUILTINS
anyway, I reckon you might as well not change the behaviour at all if
POSIXBUILTINS is not active.
- M.
[*]
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_22_04
next prev parent reply other threads:[~2016-10-23 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 3:02 Martijn Dekker
2016-10-22 18:24 ` Bart Schaefer
2016-10-23 12:00 ` Martijn Dekker [this message]
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
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=2047d07f-c5c1-6b8f-3d2d-cfcc2c06b875@inlv.org \
--to=martijn@inlv.org \
--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).