Minutes of the 5th December 2024 Teleconference Austin-1438 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 6th December 2024 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE SA OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group We set the calendar for upcoming meetings. It should be noted that after December 19 we will take a break until January 9th. There is no change in status of progress with ISO approval, although Bill Ash is looking for ways to make progress. Andrew noted that the html download bundle was now available with the online version of the standard. * Open Business Bug 1876: clarify, whether a trap action that is executed from a OPEN context where set -e is ignored, would have set -e ignored, too https://www.austingroupbugs.net/bug_view_page.php?bug_id=1876 Andrew took an action to ask shell developers to comment on this issue. (completed by sending an email to the reflector: austin-group-l:archive/latest/37925). * Current Business Bug 1879: claifications/improvements around command/exec and special built-in redirection errors https://www.austingroupbugs.net/bug_view_page.php?bug_id=1879 Accepted as marked, interpretation required, tc1-2024 tag. Andrew took an action to propose the interpretation (completed after the meeting). Interpretation response: The standard clearly states that when a special built-in utility is executed via the command utility, the special properties in the enumerated list at the beginning of Section 2.15 (on page 2526) shall not occur, and conforming implementations must conform to this. Rationale: Despite the lack of a superscript ¹ in the table, the statement in the description of the command utility is sufficient to require that a special built-in utility executed via command does not exit when a redirection error occurs. Notes to the Editor (not part of this interpretation): On page 2498 line 81135 section 2.8.1 Consequences of Shell Errors, change: shall exit to: shall exit¹ On page 2498 line 81166 section 2.8.1 Consequences of Shell Errors, change: the shell shall (respectively, may) exit from the subshell environment with a non-zero status and continue in the environment from which that subshell environment was invoked. to: the shell shall (respectively, may) exit from the subshell environment, with the exit status stated in the EXIT STATUS section for the sh utility, and continue in the environment from which that subshell environment was invoked. On page 2526 line 82346 section 2.15 Special Built-In Utilities, change: An error in a special built-in utility may cause a shell executing that utility to abort, while an error in a regular built-in utility shall not cause a shell executing that utility to abort. to: An error in a special built-in utility or redirection error with a special built-in utility may cause a shell executing that utility to abort, while for a regular built-in utility such errors shall not cause a shell executing that utility to abort. On page 2539 line 82804 section exec, change: If a redirection error occurs (see [xref to 2.8.1]), the exit status shall be a value in the range 1−125. to: If a redirection error occurs and the shell does not exit (see [xref to 2.8.1]), the exit status (of exec) shall be a value in the range 1−125. Bug 1880: Missing CX shading on text about file descriptors https://www.austingroupbugs.net/bug_view_page.php?bug_id=1880 Accepted, resolved, tc1-2024 tag Bug 1881: Alias names should not be allowed to contain https://www.austingroupbugs.net/bug_view_page.php?bug_id=1881 Accepted, resolved, tc1-2024 tag Bug 1882: read() EISDIR mentions readdir() but not posix_getdents() https://www.austingroupbugs.net/bug_view_page.php?bug_id=1882 Accepted, resolved, tc1-2024 tag Bug 1883: Standardization of troff https://www.austingroupbugs.net/bug_view_page.php?bug_id=1883 Rejected, closed. Although it would be in scope, we do not know of a group that would be willing to spend the time needed to set up, sponsor, and lead an nroff/troff working group to prepare a specification for these utilities. Without the output of such a group being available to standardize, we do not believe that we can accept a proposal to add these utilities to the standard. If you do have a complete specification that is ready to be standardized, please submit a separate bug report for consideration. Until a complete specification is available, this bug is rejected. Next Steps ---------- The next calls are on Thu 2024-12-12 (WEBEX meeting - general bugs) Thu 2024-12-19 (WEBEX meeting - general bugs) Thu 2025-01-09 (WEBEX meeting - 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)