[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001082. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001082]: "delimited" is incorrect

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1082 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001083]: "next" character is misleading

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1083 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001083. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001084]: rule 3, 4, 5 do not say that a token is started, if needed

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1084 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001084. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001085]: "token shall be from the current position in the input" is incorrect

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1085 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001085. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001086. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001086]: Token "Recognition" is misleading and the usage of "word" in that section should be clarified.

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1086 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001098]: do_group symbol cannot be accepted as written, because rule 6 cannot yield Done token

The following issue has been set as RELATED TO issue 0001100. == http://austingroupbugs.net/view.php?id=1098 == Reported By:Mark_Galeck Assign

[1003.1(2016)/Issue7+TC2 0001100]: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation.

The following issue has been set as RELATED TO issue 0001098. == http://austingroupbugs.net/view.php?id=1100 == Reported By:Mark_Galeck Assign

Re: "command" behaviour

On 2016-10-20 09:13:07 +0100, Geoff Clare wrote: > Martijn Dekker wrote, on 20 Oct 2016: > > > > | If command is not found, the exit status shall be 127. If command is > > | found, but it is not an executable utility, the exit status shall be > > | 126. If a redirection error occurs (see Consequen

Re: "command" behaviour

Vincent Lefevre wrote: > > Indeed, and interpreting this requirement to exit with status 127 if > > the command is not found as meaning that: > > > > exec nonexistentfile > > > > always causes the shell to exit, in all circumstances, conflicts with > > XCU 2.8.1 Consequences of Shell Errors

Re: "command" behaviour

Op 28-10-16 om 14:58 schreef Vincent Lefevre: > And after the > exec is handled, the shell is no longer involved, so that 2.8.1 > cannot apply in any case. But that is just the logic I was questioning in my replies to Jörg and Chet. How can the exec be "handled" if the file to exec doesn't exist?

Re: "command" behaviour

As worded the expectation I'd have is that the shell is supposed to exit, as an override of XCU 2.8.1. This puts the onus of error checking on all scripts invoking a script that makes use of exec, however, which I don't see as ideal. What is missing in the first sentence of EXIT STATUS, in < >,

Event [Austin Group teleconference +1-888-426-6840 PIN: 2115756] 2016-11-03 at 11:00 America/New_York created

BEGIN:VCALENDAR VERSION:2.0 PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.18// CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/New_York X-LIC-LOCATION:America/New_York BEGIN:STANDARD DTSTART:20161106T02 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST END:STANDARD BE

Re: Should aliases expand after 'command'?

On Mon, Oct 24, 2016 at 6:22 AM, Joerg Schilling wrote: > Martijn Dekker wrote: > >> I always thought 'command' is suitable for bypassing both aliases and >> shell functions. AT&T ksh93 defines a default alias >>command='command ' >> so that aliases after 'command' are expanded, but it is alo

Minutes of the 27th October 2016 Teleconference

All These are the minutes from this weeks call. Our next call is next thursday. Please note that as calls are anchored on US time, the call will be one hour earlier than normal in Europe regards Andrew - Minutes of the 27th October 2016 Teleconference Austin-789 Page 1 of 1 Submit