[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2020-01-20 Thread Austin Group Bug Tracker
The following issue has been set as RELATED TO issue 051. == https://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2020-01-20 Thread Austin Group Bug Tracker
The following issue has been set as RELATED TO issue 0001309. == https://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2019-11-07 Thread Austin Group Bug Tracker
The following issue has a resolution that has been APPLIED. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2019-02-11 Thread Austin Group Bug Tracker
The following issue has been UPDATED. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-13 Thread Austin Group Bug Tracker
The following issue NEEDS AN INTERPRETATION. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-13 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

Re: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-13 Thread Geoff Clare
Robert Elz wrote, on 12 Dec 2018: > > Date:Tue, 11 Dec 2018 16:33:39 + > From:Austin Group Bug Tracker > Message-ID: <83857fbeb34fcb776e74f9e733705...@austingroupbugs.net> > > > | But they're not performed by the same execution environment. > | > | From

Re: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Robert Elz
Date:Tue, 11 Dec 2018 16:33:39 + From:Austin Group Bug Tracker Message-ID: <83857fbeb34fcb776e74f9e733705...@austingroupbugs.net> | But they're not performed by the same execution environment. | | From the perspective of the assignment statement, there is

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-12-11 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2018-03-09 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-17 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-17 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

Re: order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Robert Elz
OK, when I reread the line in question more carefully, I see that it only applies in the case where there is a command word (which is not...) I think left to right is now specified (in all cases) as earlier it says... the following expansions, assignments, and redirections shall all be

Re: order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Joerg Schilling
Stephane CHAZELAS wrote: > The discussion (on austin group) I was remembering of was in > April 2010, with "Assignment with command: export only, or sets > variable, too?" as the subject. > > Followup on dash mailing list at >

Re: order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Robert Elz
Date:Fri, 16 Jun 2017 17:32:44 +0100 From:Stephane CHAZELAS Message-ID: <20170616163244.ga4...@chaz.gmail.com> | Is it really? The text that says it is still there. Line 75508 in TC2 | I do remember it was discussed some time ago

Re: order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Stephane CHAZELAS
2017-06-16 18:38:42 +0200, Joerg Schilling: [...] > > I do remember it was discussed some time ago and the outcome was > > that $b should be x. It was reported to "dash" (as a POSIX > > conformance bug) and despite initial reticence, dash was changed > > so as to perform assignments left to right

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

Re: order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Joerg Schilling
Stephane CHAZELAS wrote: > 2017-06-16 16:19:27 +, Austin Group Bug Tracker: > [...] > > In > > a=a; a=x b=$a > > it is explicitly unspecified whether b=a or b=x at > > the conclusion. It would be astounding if there was > > to be a stricter requirement

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

order of assignments (Was: [1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified)

2017-06-16 Thread Stephane CHAZELAS
2017-06-16 16:19:27 +, Austin Group Bug Tracker: [...] > In > a=a; a=x b=$a > it is explicitly unspecified whether b=a or b=x at > the conclusion. It would be astounding if there was > to be a stricter requirement for $? [...] Is it really? I do remember it was discussed some time

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-16 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-15 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To:

[1003.1(2016)/Issue7+TC2 0001150]: exit status of command substitution not properly specified

2017-06-15 Thread Austin Group Bug Tracker
The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1150 == Reported By:kre Assigned To: