Minutes of the 20th November 2023 Teleconference Austin-1362 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th 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. Andrew Josey, The Open Group Tom Thompson, IEEE Ahmet Acar * General news Andrew reported that the IEEE MEC has been resolved. We also finalized the last interpretation today. We are thus on target for issuing the next draft prior to the end of year break. Andrew noted that the action below to issue a status report is still open. We discussed the need for a general status report to be issued, describing where we are in the draft schedule and the cutoff for content to be considered into Issue 8. AI:Andrew to draft status report. 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 We revised the change and recorded as bugnote 6577: 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 currently set to either changed or changed-and-warned (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 a tri-state internal flag with the state values unchanged, changed, and changed-and-warned, which is: Initially set to unchanged Set to changed by any command that modifies the buffer Set to unchanged by an e or E command that reloads (or empties) the buffer, or a w command that writes the entire buffer Set to either changed-and-warned or unchanged by an e or q command that warns an attempt was made to destroy the editor 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 currently set to changed On page 2800 line 92844, change: ... and shall continue in command mode with the current line number unchanged. If the e or q command is repeated with no intervening command, it shall take effect. to: ... and shall continue in command mode with the buffer change flag set to either changed-and-warned or unchanged and the current line number unchanged. If another e or q command is then attempted with no intervening command that sets the buffer change flag to changed, 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 altered. 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 currently set to unchanged, 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 currently set to changed 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 the current state of the buffer change flag. 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 altered. 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 whether the buffer change flag is set to changed or left unaltered. 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 currently set to changed 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 the current state of the buffer change flag 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 alter the buffer change flag; thus, this alone ... After page 2811 line 93292 section ed RATIONALE, add a paragraph: Implementations are encouraged to set the buffer change flag to changed-and-warned when an e or q command warns that an attempt was made to destroy the editor buffer. Some existing implementations set it to unchanged, but this has the undesirable side-effect that a SIGHUP received after the warning is given does not write the buffer to ed.hup. On page 2811 line 93294, change FUTURE DIRECTIONS from "None" to: A future version of this standard may require that the buffer change flag is set to changed-and-warned when an e or q command warns that an attempt was made to destroy the editor buffer. Bug 1776: find -newer any symlinks Accepted as Marked https://austingroupbugs.net/view.php?id=1776 This item is tagged for TC3-2008 On page 2920 line 97596 section find (-newer), change: The primary shall evaluate as true if the modification time of the current file is more recent than the modification time of the file named by the pathname file. to: The primary shall evaluate as true if the modification time of the current file is more recent than the modification time of the file named by the pathname file. If file names a symbolic link, the modification time used shall be that of the file referenced by the symbolic link if either the -H or -L is specified; if neither -H nor -L is specified, it is unspecified whether the modification time is that of the symbolic link itself or of the file referenced by the symbolic link. In either case, if the referenced file does not exist, the modification time used shall be that of the link itself. If file is a relative pathname, it shall be resolved relative to the current working directory that was inherited by find when it was invoked. Next Steps ---------- The next call is on: Mon 2023-11-20 (Zoom meeting - general bugs/ballot resolution) Mon 2023-11-27 (Zoom meeting - general bugs/ballot resolution) Thu 2023-11-30 (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. Apologies in advance: Geoff Clare, 2023-11-27 Andrew Josey, 2023-11-30 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)