Minutes of the 11th August 2016 Teleconference Austin-776 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th August 2016 Attendees: Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Mark Ziegast, SHware Systems Joerg Schilling, FOKUS Fraunhofer Martin Rehak, Oracle Andrew Josey, The Open Group David Clissold, IBM Richard Hansen, Google Apologies Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat * General news Andrew noted that the TC2 publication is expected to be published on the 15th August by IEEE. Our next steps shortly, will be to move onto the full edition. We need to prepare the final frontmatter. Richard raised an issue about IPR policy. Wording has been added to the Austin Group home page to make this clear, also the policy on patents. * Outstanding actions ( Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 28 Jan 2016) Bug 0000249: Add standard support for $'...' in shell Reopened http://austingroupbugs.net/bug_view_page.php?bug_id=249 We will return to bug 249 on a future call. Bug 0000953: Alias expansion is under-specified Was Accepted as Marked http://austingroupbugs.net/view.php?id=953 Richard has an action to propose new wording to discuss in a future telecon. * Current Business Bug 0001008: 1. clarify iconv(3) reset usage; 2. truly support Unicode character input Accepted as Marked http://austingroupbugs.net/view.php?id=1008 The last sentence was added below Add to application usage as a new paragraph after P1110, L37364: It is the responsibility of the application to ensure that, if the output codeset has a locking-shift encoding, the output buffer is returned to its initial shift state when conversion is completed. This can be accomplished by calling iconv() with inbuf as a null pointer, or with inbuf pointing to a null pointer, before calling iconv_close(). Since the standard does not provide a way to query whether a codeset has a locking-shift encoding, it is recommended that applications always call iconv() in this way before calling iconv_close(). Bug 0001006: PS1 should be subject to command substitution and arithmetic expansion Accepted as Marked http://austingroupbugs.net/view.php?id=1006 This item is tagged for TC3-2008. The interpretation was updated. Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The standard does not match existing practice for several current shell implementations. Notes to the Editor (not part of this interpretation): On page 2326 lines 73832-73841, replace the entire description of PS1 with: [UP]PS1 The processing of the PS1 shell variable shall be supported if the system supports the User Portability Utilities option.[/UP] Each time an interactive shell is ready to read a command, the value of this variable shall be subjected to parameter expansion (see [xref to Section 2.6.2]) and exclamation-mark expansion (see below). Whether the value is also subjected to command substitution (see [xref to Section 2.6.3]) or arithmetic expansion (see [xref to Section 2.6.4]) or both is unspecified. After expansion, the value shall be written to standard error. The expansions shall be performed in two passes, where the result of the first pass is input to the second pass. One of the passes shall perform only the exclamation-mark expansion described below. The other pass shall perform the other expansion(s) according to the rules in [xref to Section 2.6]. Which of the two passes is performed first is unspecified. The default value shall be "$ ". For users who have specific additional implementation-defined privileges, the default may be another, implementation-defined value. Exclamation-mark expansion: The shell shall replace each instance of the character ('!') with the history file number (see [xref to sh extended description]) of the next command to be typed. Escaping the character with another character (that is, "!!") shall place the literal character in the prompt. On page 2326 lines 73842-73846, replace the entire description of PS2 with: [UP]PS2 The processing of the PS2 shell variable shall be supported if the system supports the User Portability Utilities option.[/UP] Each time the user enters a prior to completing a command line in an interactive shell, the value of this variable shall be subjected to parameter expansion (see [xref to Section 2.6.2]). Whether the value is also subjected to command substitution (see [xref to Section 2.6.3]) or arithmetic expansion (see [xref to Section 2.6.4]) or both is unspecified. After expansion, the value shall be written to standard error. The default value shall be "> ". On page 2326 lines 73847-73851, replace the entire description of PS4 with: [UP]PS4 The processing of the PS4 shell variable shall be supported if the system supports the User Portability Utilities option.[/UP] When an execution trace (set −x) is being performed in an interactive shell, before each line in the execution trace, the value of this variable shall be subjected to parameter expansion (see [xref to Section 2.6.2]). Whether the value is also subject to command substitution (see [xref to Section 2.6.3]) or arithmetic expansion (see [xref to Section 2.6.4]) or both is unspecified. After expansion, the value shall be written to standard error. The default value shall be "+ ". On page 3191 line 106776 append to the description of ENV: The file specified by ENV need not be processed if the file can be written by any user other than the user identified by the real (and effective) user ID of the shell process. Bug 1009: "remain in affect after" and "during the execution" are problematic when built-in/function modifies the variable OPEN http://austingroupbugs.net/view.php?id=1009 Next Steps ---------- The next call is on August 18, 2016 (a Thursday) Apologies in advance: Richard Hansen Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#