A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1872 
====================================================================== 
Reported By:                steffen
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1872
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Resolved
Name:                       steffen 
Organization:                
User Reference:              
Section:                    find 
Page Number:                2946 
Line Number:                98444 ff. 
Interp Status:              --- 
Final Accepted Text:        https://austingroupbugs.net/view.php?id=1872#c6956 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2024-11-07 21:34 UTC
Last Modified:              2024-11-18 09:34 UTC
====================================================================== 
Summary:                    find: clarify "less safe" statement
====================================================================== 

---------------------------------------------------------------------- 
 (0006961) geoffclare (manager) - 2024-11-18 09:34
 https://austingroupbugs.net/view.php?id=1872#c6961 
---------------------------------------------------------------------- 
> it's not totally clear what should happen if it's not used as last
argument or what the "error" entails.

The "should ... but may ..." wording allows two behaviours with one
recommended over the other. So if it's not used as last argument, the error
is required.

What happens when errors are detected is described in CONSEQUENCES OF
ERRORS. Since there is no explicit mention of this particular error in that
section on the xargs page, the default description in 1.4 Utility
Description Defaults applies. This allows all of the behaviours you
describe, making this a quality-of-implementation issue. If/when we make
the error mandatory, that would be the time to consider tightening the
allowed behaviour for this error, based on implementation behaviour(s) at
the time. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-11-07 21:34 steffen        New Issue                                    
2024-11-07 21:34 steffen        Name                      => steffen         
2024-11-07 21:34 steffen        Section                   => find            
2024-11-07 21:34 steffen        Page Number               => 2946            
2024-11-07 21:34 steffen        Line Number               => 98444 ff.       
2024-11-07 21:38 steffen        Note Added: 0006951                          
2024-11-08 01:40 steffen        Note Added: 0006952                          
2024-11-08 01:42 steffen        Note Edited: 0006952                         
2024-11-08 08:31 stephane       Note Added: 0006953                          
2024-11-12 09:48 geoffclare     Note Added: 0006954                          
2024-11-13 18:19 steffen        Note Edited: 0006952                         
2024-11-14 17:03 geoffclare     Note Added: 0006956                          
2024-11-14 17:04 geoffclare     Interp Status             => ---             
2024-11-14 17:04 geoffclare     Final Accepted Text       =>
https://austingroupbugs.net/view.php?id=1872#c6956    
2024-11-14 17:04 geoffclare     Status                   New => Resolved     
2024-11-14 17:04 geoffclare     Resolution               Open => Accepted As
Marked
2024-11-14 17:05 geoffclare     Tag Attached: tc1-2024                       
2024-11-14 17:08 geoffclare     Note Edited: 0006956                         
2024-11-16 08:54 stephane       Note Added: 0006957                          
2024-11-16 19:42 steffen        Note Added: 0006958                          
2024-11-17 03:03 philip-guentherNote Added: 0006959                          
2024-11-17 08:17 stephane       Note Added: 0006960                          
2024-11-17 08:21 stephane       Note Edited: 0006960                         
2024-11-18 09:34 geoffclare     Note Added: 0006961                          
======================================================================


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

Reply via email to