A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1538 
====================================================================== 
Reported By:                andras_farkas
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1538
Category:                   Shell and Utilities
Type:                       Error
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Andras Farkas 
Organization:                
User Reference:              
Section:                    what 
Page Number:                3437 
Line Number:                116041 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2021-12-05 06:48 UTC
Last Modified:              2022-02-17 17:00 UTC
====================================================================== 
Summary:                    what -s is poorly described, uses the word "quit"
====================================================================== 

---------------------------------------------------------------------- 
 (0005675) geoffclare (manager) - 2022-02-17 17:00
 https://austingroupbugs.net/view.php?id=1538#c5675 
---------------------------------------------------------------------- 
Interpretation response
------------------------
The standard states the output produced by the <i>what</i> utility includes
the name of the file for each occurrence of the pattern found and that no
output is produced for a file that has no occurrences of the pattern, and
conforming implementations must conform to this. However, concerns have
been raised about this which are being referred to the sponsor.

Rationale:
-------------
Implementations write the pathname once for each file, regardless of how
many identification strings are found in it.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
On page 3437 line 116038 (-s option), change:<blockquote>Quit after finding
the first occurrence of the pattern in each
file.</blockquote>to:<blockquote>Skip to the next <i>file</i> operand (if
any) after finding the first occurrence of the pattern in each
file.</blockquote>
On page 3437 line 116063 (STDOUT), change:<blockquote>The standard output
shall consist of the following for each <i>file</i>
operand:<pre>"%s:\n\t%s\n", <<i>pathname</i>>, <<i>identification
string</i>></pre></blockquote>to:<blockquote>The standard output for each
<i>file</i> operand shall consist of:<pre>"%s:\n",
<<i>file</i>></pre>followed by one line for each identification string (if
any) found in the file, in the following format:<pre>"\t%s\n", 
<identification string></pre></blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2021-12-05 06:48 andras_farkas  New Issue                                    
2021-12-05 06:48 andras_farkas  Name                      => Andras Farkas   
2021-12-05 06:48 andras_farkas  Section                   => what            
2022-02-17 09:02 Don Cragun     Page Number               => 3437            
2022-02-17 09:02 Don Cragun     Line Number               => 116041          
2022-02-17 09:02 Don Cragun     Interp Status             => ---             
2022-02-17 15:57 geoffclare     Note Added: 0005674                          
2022-02-17 17:00 geoffclare     Note Added: 0005675                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to