Martijn Dekker via austin-group-l at The Open Group dixit:
> Today I received a pull request to make allexport work for ${var:=value} and
> ${var=value} on ksh 93u+m. This currently works on bash, dash, *BSD sh, and
> zsh, but not on ksh, pdksh/mksh, or yash.
mksh does so because AT ksh does;
Op 17-01-22 om 22:54 schreef Robert Elz:
Date:Sun, 16 Jan 2022 20:26:00 +
From:"Martijn Dekker via austin-group-l at The Open Group"
Message-ID: <409b0a89-6fe1-d688-23f9-8c918ef89...@inlv.org>
| I need some clarity. Should ${var:=value} and ${var=value}
Date:Sun, 16 Jan 2022 20:26:00 +
From:"Martijn Dekker via austin-group-l at The Open Group"
Message-ID: <409b0a89-6fe1-d688-23f9-8c918ef89...@inlv.org>
| I need some clarity. Should ${var:=value} and ${var=value} honour
| allexport?
Yes.
Any assignment
Op 14-08-18 om 17:21 schreef Stephane Chazelas:
Hi, the spec for the "allexport" (set -a) shell option says:
POSIX2018> When this option is on, the export attribute shall
POSIX2018> be set for each variable to which an assignment is
POSIX2018> performed; see XBD Variable Assignment. If the
On 8/14/18 6:42 PM, Robert Elz wrote:
> For the NetBSD shell, the order is, more or less, read the environment,
> import variables found there and mark them as exported. Set the
> vars that POSIX (of just the shell) defines as set at startup, process
> the command line options, deal with $ENV,
Date:Wed, 15 Aug 2018 05:42:46 +0700
From:Robert Elz
Message-ID: <29705.1534286...@jinx.noi.kre.to>
| LINENO is "magic": in that is isnn't really assigned as a variable, rather
the
[...]
| to those (PWD and the others, like RANDOM) so -a is irrelevant.
Oops, I
Hi, the spec for the "allexport" (set -a) shell option says:
POSIX2018> When this option is on, the export attribute shall
POSIX2018> be set for each variable to which an assignment is
POSIX2018> performed; see XBD Variable Assignment. If the
POSIX2018> assignment precedes a utility name in a
