A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1913 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1913
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:             Shell & Utilities 
Section:                    2.7.5, 2.7.6 
Page Number:                2497 
Line Number:                81097-81118 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2025-03-12 03:33 UTC
Last Modified:              2025-03-13 20:20 UTC
====================================================================== 
Summary:                    clarify/define the meaning of n<&n and m>&m
redirections
====================================================================== 

---------------------------------------------------------------------- 
 (0007119) larryv (reporter) - 2025-03-13 20:20
 https://www.austingroupbugs.net/view.php?id=1913#c7119 
---------------------------------------------------------------------- 
https://www.austingroupbugs.net/view.php?id=1913#c7117:<blockquote>so what about
things like <1 or >0 ?</blockquote>The former is covered by section 2.7.1 and
redirects stdin from a file literally named "1"; the latter is covered by
section 2.7.2 and redirects stdout to a file literally named "0". This report
isn't about those forms of redirection.<blockquote>As far as I understand the
wording about the n = word case, wouldn't that also mean that e.g.:
   exec 8<some file; exec 8<8; utility
would now be expected to keep FD 8 open when invoking utility</blockquote>I
don't see how, assuming you actually mean<pre>exec 8<<i>somefile</i>; exec 8<&8;
<i>utility</i></pre>The proposed wording says (emphasis mine):<blockquote>if the
shell would have closed the file descriptor because it was opened using exec and
has a value greater than 2, <b>when the redirection is being performed in a
command that will execute a non-built-in utility</b>, the file descriptor shall
instead remain open when the utility is executed</blockquote>Your second
<i>exec</i> command isn't executing a non-built-in utility. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-03-12 03:33 calestyo       New Issue                                    
2025-03-12 07:00 larryv         Note Added: 0007111                          
2025-03-13 02:41 calestyo       Note Added: 0007112                          
2025-03-13 16:12 geoffclare     Note Added: 0007115                          
2025-03-13 17:48 calestyo       Note Added: 0007117                          
2025-03-13 20:20 larryv         Note Added: 0007119                          
======================================================================


            • ... Harald van Dijk via austin-group-l at The Open Group
              • ... Geoff Clare via austin-group-l at The Open Group
              • ... Harald van Dijk via austin-group-l at The Open Group
              • ... Steffen Nurpmeso via austin-group-l at The Open Group
              • ... Chet Ramey via austin-group-l at The Open Group
            • ... Chet Ramey via austin-group-l at The Open Group
          • ... Chet Ramey via austin-group-l at The Open Group
        • ... Lawrence Velázquez via austin-group-l at The Open Group
          • ... Harald van Dijk via austin-group-l at The Open Group
  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
  • Fwd: Re: [... Chet Ramey via austin-group-l at The Open Group
    • Re: F... Geoff Clare via austin-group-l at The Open Group
      • R... Chet Ramey via austin-group-l at The Open Group
        • ... Geoff Clare via austin-group-l at The Open Group
          • ... Chet Ramey via austin-group-l at The Open Group
            • ... Geoff Clare via austin-group-l at The Open Group
              • ... Chet Ramey via austin-group-l at The Open Group
              • ... Geoff Clare via austin-group-l at The Open Group

Reply via email to