Re: Syntax error with "command . file" (was: [1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script)

2023-03-10 Thread Harald van Dijk via austin-group-l at The Open Group
Based on past experiences, I am assuming the e-mail this is a reply to was meant to be sent to the list and I am quoting it in full and replying on the list for that reason. On 10/03/2023 21:24, Robert Elz wrote: Date:Fri, 10 Mar 2023 18:13:00 + From:"Harald van

[1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1629 == Reported By:mirabilos Assigned To:

Re: Syntax error with "command . file" (was: [1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script)

2023-03-10 Thread Robert Elz via austin-group-l at The Open Group
Date:Fri, 10 Mar 2023 18:13:00 + From:"Harald van Dijk via austin-group-l at The Open Group" Message-ID: | Other shells that exit are bosh, yash, and my own. It's both what POSIX | currently requires (contrary to what kre wrote on the bug) That's not how

Re: Syntax error with "command . file" (was: [1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script)

2023-03-10 Thread Harald van Dijk via austin-group-l at The Open Group
On 10/03/2023 17:12, Geoff Clare via austin-group-l at The Open Group wrote: -- (0006200) kre (reporter) - 2023-03-10 14:52 https://www.austingroupbugs.net/view.php?id=1629#c6200

Re: Syntax error with "command . file" (was: [1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script)

2023-03-10 Thread Robert Elz via austin-group-l at The Open Group
Date:Fri, 10 Mar 2023 17:12:50 + From:"Geoff Clare via austin-group-l at The Open Group" Message-ID: | All of bash, ksh88, ksh93, dash and mksh reported the syntax error and | then executed the echo command (which output a non-zero number). yash and bosh

Syntax error with "command . file" (was: [1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script)

2023-03-10 Thread Geoff Clare via austin-group-l at The Open Group
> -- > (0006200) kre (reporter) - 2023-03-10 14:52 > https://www.austingroupbugs.net/view.php?id=1629#c6200 > -- > Re

[1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1629 == Reported By:mirabilos Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1629 == Reported By:mirabilos Assigned To:

[Issue 8 drafts 0001631]: Default archive rules are incompatible with parallel processing.

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1631 == Reported By:dmitry_goncharov

[Issue 8 drafts 0001626]: Reconsider CURDIR macro

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1626 == Reported By:illiliti Assigned

[Issue 8 drafts 0001624]: getdelim() / getline() non-success reporting clarification

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1624 == Reported By:romanzilka

[1003.1(2016/18)/Issue7+TC2 0001629]: Shell vs. read(2) errors on the script

2023-03-10 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1629 == Reported By:mirabilos Assigned To: