Minutes of the 7th April 2022 Teleconference Austin-1212 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8th April 2022 Attendees: Mark Ziegast, SHware Systems Dev. Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Andrew Josey, The Open Group Eric Ackermann, HPI, University of Potsdam * General news This was a call dedicated to general bugs. * Outstanding actions Bug 1533: struct tm: add tm_gmtoff (and tm_zone) field(s) OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1533 This was discussed in the February 3, 2022 teleconference. Leave it open until we get a more complete suggestion for the Desired Action. * Current Business Bug 1544: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout https://austingroupbugs.net/view.php?id=1544 Open Andrew completed the action to get feedback from IBM. The feedback was as follows: We had some discussion in AIX and the only issue we see is currently "-" is treated a file with -o. If uudecode is used with "-o -" then a file with "-" is created but with new changes this will be a change in behaviour for customers. If someone is already using "-" for file then they need to change. Other than that I think this will be new functionality needs to be implemented to compliant with SUS v8. Bug 1546: BREs: reserve \? \+ and \| Accepted as Marked https://austingroupbugs.net/view.php?id=1546 There have been further comments made on the resolution in note 5755. Changed the definition of "escape sequence" to: An escape sequence is defined as the escape character followed by any single character, which is thereby "escaped". The escape character is a that is neither in a bracket expression nor itself escaped. See https://austingroupbugs.net/view.php?id=1546#c5755 for details Bug 1550: clarifications/ambiguities in the description of context addresses and their delimiters for sed OPEN https://austingroupbugs.net/view.php?id=1550 Geoff had completed his action to propose wording as suggested in bugnote 5756 Leave open for feedback (ongoing discussion). Bug 1551: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters) OPEN https://austingroupbugs.net/view.php?id=1551 Geoff had completed his action to propose wording as suggested in bugnote 5756 This is expected to be closed as a dup of 1550. Bug 1556: clarify meaning of \n used in a bracket expression in a sed context address or s-command OPEN https://austingroupbugs.net/view.php?id=1556 Aim to close as a dup of 1550 when we resolve 1550. Bug 1557: Better wording to describe FD_CLOEXEC. Rejected https://austingroupbugs.net/view.php?id=1557 Re: Note: 0005651 In order to have consistent wording across open(), pipe2(), dup3(), accept4(), it would be necessary to drastically rearrange the descriptions of the last three, so that the new function with the flags argument is described first and then the old function is said to be equivalent to that function with a flags argument of 0. (Instead of the new function being said to be equivalent to the old function, except ...) This seems like a lot of work for little gain. Bug 1558: require [^...] in addition to [!...] for bracket expression negation Rejected https://austingroupbugs.net/view.php?id=1558 This bug is rejected because there is no consensus to make the requested change. Bug 1559: Participants, notice.html: small typo (compenstation to compensation) OPEN https://austingroupbugs.net/view.php?id=1559 Action: Andrew to fix the HTML edition Bug 1560: clarify wording of command substitution OPEN https://austingroupbugs.net/view.php?id=1560 We are leaning towards accepting the first part of the desired action, but should leave this open in case it is affected by the related bugs 1561, 1562 and 1564. We will continue this next time Next Steps ---------- The next calls are on: Mon 2022-04-11 (gettext) Thu 2022-04-14 (general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup)