Minutes of the 27th January 2022 Teleconference    Austin-1193 Page 1 of 1
Submitted by Andrew Josey, The Open Group.       28th January 2022

Attendees:
    Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
    Don Cragun, IEEE PASC OR
    Geoff Clare, The Open Group
    Andrew Josey, The Open Group  (Partial)
    Eric Blake, Red Hat, The Open Group OR
    Mark Ziegast, SHware Systems Dev.

Apologies
    Eric Ackermann, HPI, University of Potsdam

* General news

This was a call dedicated to General bugs.

* Outstanding actions

None.


* Current Business

Bug 1529: ex: follow-up to issue #1440 Accepted as Marked
https://austingroupbugs.net/bug_view_page.php?bug_id=1529

This item is tagged for Issue 8.

Change the synopsis of the Escape command on P2730, L89413-89414 from:
    ! command
    [addr]! command
to:
    !command
    [addr]!command

Add a new paragraph to APPLICATION USAGE following P2743, L89822:
    Unlike the system() function, ex does not pass "--" between the
    "-c" option and the command string, so that programs for which
    -c takes an option-argument can be used in the shell edit option.
    Users who want to use an escape command to execute a utility
    whose name starts with <tt>'-'</tt> or <tt>'+'</tt> need to
    provide a pathname for that utiity that does not start with
    either of those characters, or precede the utility name with a
    <blank> character.

Add a new section to the ex RATIONALE on P2756, before L90368:
    Escape

    In Issue 8 the system() function (see xref to system()) was
    changed to require that the POSIX shell be invoked with
    <tt>"sh"</tt>, <tt>"-c"</tt>, <tt>"--"</tt>, and command arguments
    to make it easier to execute programs with <hyphen-minus> ('-')
    or <plus-sign> ('+') as the first character of the program's
    filename. A similar request to have the ex escape do the same
    was not accepted. Unlike system() (which always invokes a POSIX
    shell), ex invokes the program named by the shell option. For
    example, the csh and tcsh shells that are frequently used as
    login shells do not recognize <tt>--</tt> after <tt>-c</tt> as
    an end-of-options indicator. The program need not even be one
    that recognizes any POSIX shell command line syntax. Some users
    invoke shell scripts to process lines that are being supplied
    to the specified utility These utilities know that they will
    be given <tt>-c</tt> as a first argument and just ignore it.
    Any utilities used in this manner would have to be modified to
    skip over another argument (the <tt>--</tt>) to find the desired
    argument.


Bug 1530: nohup: follow-up to issue #1440  Accepted
https://austingroupbugs.net/bug_view_page.php?bug_id=1530

This item is tagged for TC3-2008.

Bug 1531: time: follow-up to issue #1440 Accepted
https://austingroupbugs.net/bug_view_page.php?bug_id=1531

This item is tagged for TC3-2008.

Bug1532: "stty -g" output should not have to be split
https://austingroupbugs.net/bug_view_page.php?bug_id=1532

We will continue on this item next time.

Next Steps
----------
The next calls are on:
    Mon 2022-01-31 (gettext) 
    Thu 2022-02-03 (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)