[Issue 8 drafts 0001743]: mailx: revert faulty change
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1743 == Reported By:steffen Assigned To: == Project:Issue 8 drafts Issue ID: 1743 Category: Shell and Utilities Type: Error Severity: Editorial Priority: normal Status: New Name: steffen Organization: User Reference: Section:mailx Page Number:3085, 3087 Line Number:103783, 103869 Final Accepted Text: == Date Submitted: 2023-06-08 20:48 UTC Last Modified: 2023-06-20 18:24 UTC == Summary:mailx: revert faulty change == -- (0006342) steffen (reporter) - 2023-06-20 18:24 https://austingroupbugs.net/view.php?id=1743#c6342 -- But what current POSIX defines is a sane approach, and work has been put into it so that it is like that. And it mirrors what other MUAs do (mutt for example). And it can be implemented on all codebases in a few minutes. If it is not too much work you could close this. The only real thing is on page 3087, line 103862 ff., insert after [.] for example, when hlj is an alias, h...@posix.com does not trigger the alias substitution. the sentences Recursive expansion of an alias group member can be prevented by prefixing it with an unquoted . describing status quo of all codebases; i open a different issue on that. Sorry. "Despair" on my side: if you read documentation and see the clean approach of a from-scratch implementation like from mutt, for example, with slightly different meaning of metoo, alternates and alias. Issue History Date ModifiedUsername FieldChange == 2023-06-08 20:48 steffenNew Issue 2023-06-08 20:48 steffenName => steffen 2023-06-08 20:48 steffenSection => mailx 2023-06-08 20:48 steffenPage Number => 3085, 3087 2023-06-08 20:48 steffenLine Number => 103783, 103869 2023-06-09 13:17 steffenNote Added: 0006317 2023-06-10 16:39 steffenNote Added: 0006318 2023-06-13 14:51 geoffclare Project 1003.1(2016/18)/Issue7+TC2 => Issue 8 drafts 2023-06-20 18:24 steffenNote Added: 0006342 ==
[1003.1(2016/18)/Issue7+TC2 0001747]: mailx: document alias expansion prevention
The following issue has been SUBMITTED. == https://austingroupbugs.net/view.php?id=1747 == Reported By:steffen Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1747 Category: Shell and Utilities Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: steffen Organization: User Reference: Section:mailx Page Number:3087 Line Number:103862 Interp Status: --- Final Accepted Text: == Date Submitted: 2023-06-20 18:28 UTC Last Modified: 2023-06-20 18:28 UTC == Summary:mailx: document alias expansion prevention Description: All BSD Mail and System V10 mailx codebases support prevention of alias expansion via reverse solidus / backslash. Desired Action: On page 3087, line 103862 ff., append after [.] for example, when hlj is an alias, h...@posix.com does not trigger the alias substitution. the sentence Recursive expansion of an alias group member can be prevented by prefixing it with an unquoted . == Issue History Date ModifiedUsername FieldChange == 2023-06-20 18:28 steffenNew Issue 2023-06-20 18:28 steffenName => steffen 2023-06-20 18:28 steffenSection => mailx 2023-06-20 18:28 steffenPage Number => 3087 2023-06-20 18:28 steffenLine Number => 103862 ==
[1003.1(2016/18)/Issue7+TC2 0001746]: fuser output format clarification
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1746 == Reported By:geoffclare Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1746 Category: Shell and Utilities Type: Clarification Requested Severity: Objection Priority: normal Status: New Name: Geoff Clare Organization: The Open Group User Reference: Section:fuser Page Number:2817 Line Number:92698 Interp Status: --- Final Accepted Text: == Date Submitted: 2023-06-13 15:58 UTC Last Modified: 2023-06-20 15:56 UTC == Summary:fuser output format clarification == -- (0006341) geoffclare (manager) - 2023-06-20 15:56 https://austingroupbugs.net/view.php?id=1746#c6341 -- New proposal that (I hope) addresses all the points raised so far... On page 2816 line 92653 section fuser (NAME), change:list process IDs of all processes that have one or more files opento:list process IDs of all processes that are using one or more named files On page 2816 line 92657 section fuser (DESCRIPTION), change:The fuser utility shall write to standard output the process IDs of processes running on the local system that have one or more named files open. For block special devices, all processes using any file on that device are listed. The fuser utility shall write to standard error additional information about the named files indicating how the file is being used. Any output for processes running on remote systems that have a named file open is unspecified. A user may need appropriate privileges to invoke the fuser utility.to:For each file operand, in order, fuser shall write one line of output, some of it to standard output, and the rest to standard error, giving information about processes running on the local system that are using the file. A process shall be considered to be using a file if it has at least one open file descriptor associated with the file or if the file is a directory that is the current working directory or the root directory for the process, and may be considered to be using a file for other implementation-dependent reasons. If file names a block special device that contains a mounted file system, and the -f option is not specified, any processes using any file on that mounted file system and any processes that are using the device file itself shall be listed. Any output for processes running on remote systems that are using a named file is unspecified. A user may need appropriate privileges to invoke the fuser utility. When standard output and standard error are directed to the same file, the output for each file operand shall be interleaved so that it is written to the file in the following order: On standard error, a pathname for the file, immediately followed by a and zero or more characters. The pathname shall be either the file operand (unaltered) or the pathname that would result from a successful call to the realpath() function, defined in System Interfaces volume of POSIX.1-202x, with the file operand as its file_name argument. For each process using the file:On standard output, the process ID in the format:" %1d",On standard error, information about the file's use by the process, in the following format:"%s",
[1003.1(2016/18)/Issue7+TC2 0001645]: execvp( ) requirements on arg0 are too strict
The following issue has been UPDATED. == https://www.austingroupbugs.net/view.php?id=1645 == Reported By:eblake Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1645 Category: System Interfaces Type: Clarification Requested Severity: Objection Priority: normal Status: Interpretation Required Name: Eric Blake Organization: Red Hat User Reference: ebb.execvp Section:XSH exec Page Number:784 Line Number:26548 Interp Status: Approved Final Accepted Text: https://www.austingroupbugs.net/view.php?id=1645#c6281 == Date Submitted: 2023-03-22 19:47 UTC Last Modified: 2023-06-20 10:55 UTC == Summary:execvp( ) requirements on arg0 are too strict == Relationships ID Summary -- related to 953 Alias expansion is under-specified related to 0001674 may posix_spawnp() fail with ENOEXEC? == -- (0006340) ajosey (manager) - 2023-06-20 10:55 https://www.austingroupbugs.net/view.php?id=1645#c6340 -- Interpretation approved: 20 June 2023 Issue History Date ModifiedUsername FieldChange == 2023-03-22 19:47 eblake New Issue 2023-03-22 19:47 eblake Name => Eric Blake 2023-03-22 19:47 eblake Organization => Red Hat 2023-03-22 19:47 eblake User Reference=> ebb.execvp 2023-03-22 19:47 eblake Section => XSH exec 2023-03-22 19:47 eblake Page Number => 784 2023-03-22 19:47 eblake Line Number => 26548 2023-03-22 19:47 eblake Interp Status => --- 2023-03-22 19:55 eblake Description Updated 2023-03-22 20:05 eblake Relationship added related to 953 2023-03-22 20:35 eblake Note Added: 0006226 2023-03-22 21:19 eblake Description Updated 2023-03-23 08:11 lacos Note Added: 0006228 2023-03-23 10:53 bastienIssue Monitored: bastien 2023-03-23 10:53 bastienNote Added: 0006231 2023-03-23 11:11 lacos Issue Monitored: lacos 2023-04-19 17:26 eblake Relationship added related to 0001674 2023-05-11 16:05 geoffclare Note Added: 0006281 2023-05-11 16:07 geoffclare Interp Status--- => Pending 2023-05-11 16:07 geoffclare Final Accepted Text => https://www.austingroupbugs.net/view.php?id=1645#c6281 2023-05-11 16:07 geoffclare Status New => Interpretation Required 2023-05-11 16:07 geoffclare Resolution Open => Accepted As Marked 2023-05-11 16:07 geoffclare Tag Attached: tc3-2008 2023-05-12 08:30 ajosey Interp StatusPending => Proposed 2023-05-12 08:30 ajosey Note Added: 0006284 2023-06-20 10:55 ajosey Interp StatusProposed => Approved 2023-06-20 10:55 ajosey Note Added: 0006340 ==
[Issue 8 drafts 0001695]: Description of MAKEFLAGS has confusing cross reference to word splitting
The following issue has been CLOSED == https://austingroupbugs.net/view.php?id=1695 == Reported By:rillig Assigned To: == Project:Issue 8 drafts Issue ID: 1695 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: Closed Name: Roland Illig Organization: User Reference: Section:make Page Number:3106 Line Number:104594 Final Accepted Text: Resolution: Duplicate Duplicate: 0 Fixed in Version: == Date Submitted: 2023-05-07 12:04 UTC Last Modified: 2023-06-20 08:40 UTC == Summary:Description of MAKEFLAGS has confusing cross reference to word splitting == Relationships ID Summary -- duplicate of0001653 make: confusing reference to word expan... == Issue History Date ModifiedUsername FieldChange == 2023-05-07 12:04 rillig New Issue 2023-05-07 12:04 rillig Name => Roland Illig 2023-05-07 12:04 rillig Section => make 2023-05-07 12:04 rillig Page Number => 3106 2023-05-07 12:04 rillig Line Number => 104594 2023-06-05 11:01 geoffclare Note Added: 0006308 2023-06-05 11:01 geoffclare Relationship added related to 0001653 2023-06-05 12:37 rillig Note Added: 0006309 2023-06-19 15:25 nick Status New => Resolved 2023-06-19 15:25 nick Resolution Open => Duplicate 2023-06-19 15:27 nick Relationship replacedduplicate of 0001653 2023-06-20 08:40 geoffclare Status Resolved => Closed ==
