Minutes of the 16th November 2023 Teleconference    Austin-1362 Page 1 of 1
Submitted by Andrew Josey, The Open Group.         17th 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 

Apologies
   Tom Thompson, IEEE

* General news

On action items from last time:

Eric raised an issue with the Etherpad and its use of non-open source javascript:
AI:Andrew took an action to contact Richard Hansen to make him aware of the issue.
Response:Andrew completed the action

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.
AI:Andrew and Geoff will meet on Thursday to finalize the response to IEEE
and submit prior to the meeting.
Response:Andrew and Geoff met and a final response to the D3 MEC
comments was sent to the IEEE editor.  After the meeting a reply
was received from IEEE accepting our response, thus completing the
requirement to address the MEC comments for the next draft.

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).

We discussed the future meeting schedule and did not set a date yet after the November 20th meeting.
We will discuss at that meeting.

* 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         Reopened
https://austingroupbugs.net/view.php?id=1786

This was reopened since we had received feedback from the GNU ed maintainer in bugnote 6570.

A response was added in bugnote 6571 and the bug left open for further response.

Based on Note: 0006570, we did some more investigation into existing
implementations. It appears that most implementations clear the
buffer change flag on an 'e' or 'q' that warned about a modified
buffer, as in the following behavior:

    $ ed
    a
    text
    .
    q
    ?
    a
    .
    q
    $

where GNU ed was the outlier.

The following modifications to the changes suggested at lines 92730
and 92845 in Note: 0006567 would capture that:

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 a w command that writes the entire buffer, or by an
    e, E, or q command. 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 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 cleared 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, it shall take effect.

We will continue on this item next time.


Bug 1775: si_addr description confusingly over-specific Accepted
https://austingroupbugs.net/view.php?id=1775

This item is tagged for TC3-2008.


Bug 1776: find -newer any symlinks OPEN
https://austingroupbugs.net/view.php?id=1776

We discussed this item and notes were made in the etherpad. We will pick up on this item next time.


Next Steps
----------

The next call is on:

  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.

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)