Minutes of the 13th November 2023 Teleconference Austin-1361 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 14th November 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Ahmet Acar Andrew Josey, The Open Group Apologies Tom Thompson, IEEE * General news Eric raised an issue with the Etherpad and its use of non-open source javascript: Administrivia: Antonio Diaz (maintainer of GNU ed) commented off-list that he was unable to review the Etherpad for on-going notes about potential changes to ed requirements, because the Etherpad depends on Javascript that does not include an open-source license (which he has disabled in his browser). Possible solutions: capture pdf renderings of the etherpad after the meeting for posting somewhere? AI:Andrew took an action to contact Richard Hansen to make him aware of the issue. Andrew confirmed that on 08 Nov 2023 the IEEE SA Standards Board approved the PAR extension request of P1003.1 Standard for Information Technology--Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 8 until 31 Dec 2024. A copy of the revised PAR (Project Authorization Request) has been added to the document register as document Austin/1360, see http://www.opengroup.org/austin/docreg.html. Andrew noted that due to a recent change in The Open Group systems now he also has to assign a role for users requesting GitLab access, so any new users will have to contact him to be setup. This does not impact existing users. Don reminded us of the need to resolve the IEEE MEC comments on draft 3, to enable us to be able to submit draft 4 when we are ready. Andrew and Geoff will meet on Thursday to finalize the response to IEEE and submit prior to the meeting. A reminder that there is no meeting on November 23rd (US Thanksgiving). * Current Business Note for issue resolution all items are tagged for Issue 8 unless noted otherwise or disposition is reject or duplicate. Bug 1786: ed behavior on non-existing filename Accepted as Marked. https://austingroupbugs.net/view.php?id=1786 Eric took an action to point the GNU ed maintainer at the resolution, and if he finds any problems then we may reopen it. On page 2797 line 92714 section ed ASYNCHRONOUS EVENTS, change: If the buffer is not empty and has changed since the last write, the to: If the buffer is not empty and the buffer change flag is set (see the EXTENDED DESCRIPTION section), the On page 2797 line 92725 section ed STDERR, change: The standard error shall be used only for diagnostic messages. to: The standard error shall be used for diagnostic messages and may be used for warning messages. On page 2797 line 92730 section ed EXTENDED DESCRIPTION, after: The ed utility shall operate on a copy of the file it is editing; changes made to the copy shall have no effect on the file until a w (write) command is given. The copy of the text is called the buffer. add these sentences: The ed utility shall keep track of whether the buffer has been modified. This shall be maintained as if via an internal flag which is set by any command that modifies the buffer and is cleared by an e or E command that reloads (or empties) the buffer, or a w command that writes the entire buffer. A command that makes changes to the buffer in such a way that its contents are the same after the command (for example s/a/a/) shall be considered to have modified the buffer, unless explicitly stated otherwise. In the remainder of the description, this flag is referred to as the buffer change flag. On page 2800 line 92839 section ed EXTENDED DESCRIPTION, change: If changes have been made in the buffer since the last w command that wrote the entire buffer to: If the buffer change flag is set On page 2800 line 92845, change: If the e or q command is repeated with no intervening command, it shall take effect. to: If another e or q command is then attempted with no intervening command that sets the buffer change flag, it shall take effect. On page 2801 line 92881, in the Append Command text, add a sentence: If is empty (that is, the terminating '.' immediately follows the 'a'), the buffer change flag shall not be set. On page 2801 line 92901, in the Edit Command text, after the sentence: If no pathname is given, the currently remembered pathname, if any, shall be used (see the f command). insert another sentence: If the pathname names a file that does not exist and the buffer change flag is clear, it is unspecified whether this is treated as an error, or whether the resulting buffer is emptied and a warning is written to standard error instead of writing the byte count to standard out. On page 2801 line 92909, in the Edit Command text, change: If the buffer has changed since the last time the entire buffer was written to: If the buffer change flag is set On page 2802 line 92914, in the Edit Without Checking Command text, change: shall not check to see whether any changes have been made to the buffer since the last w command. to: shall not check to see whether the buffer change flag is set. On page 2802 line 92918, in the Filename Command text, change: If file is given, the f command shall change the currently remembered pathname to file; to: If file is given, the f command shall change the currently remembered pathname to file, whether or not file names an existing file; On page 2803 line 92977, in the Insert Command text, add a sentence: If is empty (that is, the terminating '.' immediately follows the 'i'), the buffer change flag shall not be set. On page 2805 Read Command, add a new paragraph at the end (after line 93044): If the number of bytes read is 0 it is unspecified if the buffer change flag is set. On page 2805 line 93027, in the Quit Command text, change: If the buffer has changed since the last time the entire buffer was written to: If the buffer change flag is set On page 2805 line 93031, in the Quit Without Checking Command text, change: without checking whether changes have been made in the buffer since the last w command to: without checking whether the buffer change flag is set On page 2807 line 93120, in the Write Command text, change: This usage of the write command with '!' shall not be considered as a ``last w command that wrote the entire buffer'', as described previously; thus, this alone ... to: This usage of the w command with '!' shall not clear the buffer change flag; thus, this alone ... Next Steps ---------- The next call is on: Thu 2023-11-16 (Zoom meeting - general bugs/ballot resolution) Mon 2023-11-20 (Zoom meeting - general bugs/ballot resolution) There is no call on 2023-11-23 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)