A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1778 
====================================================================== 
Reported By:                kre
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1778
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Robert Elz 
Organization:                
User Reference:              
Section:                    XCU 3/read 
Page Number:                3291-3294 
Line Number:                111869-111878, 111961-111963, 11946, 11979-11980 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-10-02 13:58 UTC
Last Modified:              2023-10-12 18:54 UTC
====================================================================== 
Summary:                    The read utility needs field splitting
updates/corrections )and a little more)
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001649 Field splitting is woefully under speci...
====================================================================== 

---------------------------------------------------------------------- 
 (0006532) kre (reporter) - 2023-10-12 18:54
 https://www.austingroupbugs.net/view.php?id=1778#c6532 
---------------------------------------------------------------------- 
One more thing, in https://www.austingroupbugs.net/view.php?id=1778#c6510, I
ended with the following paragraph:

  While I'm here, the current text also doesn't say what to do if there's
  an error making one of those assignments - certainly read exits with a
  status > 1 in that case, that's clear, but is read expected to go ahead
  and assign to the other variables, or may it abort processing as soon as
  the error is detected?  That's unstated as well as best I can tell.
  As a hint: not all shells do the same thing here, there are actually 3
  different behaviours I have detected. Further not all shells do the >1
  exit status either, some exit 1 in this case (for some the shell (or
subshell)
  exits (treating this as a variable assignment error and doing as
specified
  by table 2.8.1 I presume).

As best I can see, the proposed resolution in
https://www.austingroupbugs.net/view.php?id=1778#c6526 does not
address
this issue.  We should be fixing this one as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-10-02 13:58 kre            New Issue                                    
2023-10-02 13:58 kre            Name                      => Robert Elz      
2023-10-02 13:58 kre            Section                   => XCU 3/read      
2023-10-02 13:58 kre            Page Number               => 3291-3294       
2023-10-02 13:58 kre            Line Number               => 111869-111878,
111961-111963, 11946, 11979-11980
2023-10-02 14:00 kre            Note Added: 0006500                          
2023-10-02 14:02 kre            Note Edited: 0006500                         
2023-10-02 14:20 kre            Note Added: 0006502                          
2023-10-02 14:22 kre            Note Edited: 0006502                         
2023-10-02 14:24 kre            Note Edited: 0006502                         
2023-10-02 14:30 kre            Note Added: 0006503                          
2023-10-02 14:33 kre            Note Edited: 0006502                         
2023-10-02 14:34 kre            Note Edited: 0006502                         
2023-10-02 14:44 kre            Note Edited: 0006500                         
2023-10-02 16:18 geoffclare     Project                  1003.1(2013)/Issue7+TC1
=> Issue 8 drafts
2023-10-02 16:19 geoffclare     version                   => Draft 3         
2023-10-02 16:20 geoffclare     Note Added: 0006507                          
2023-10-02 16:21 geoffclare     Relationship added       related to 0001649  
2023-10-03 09:23 geoffclare     Note Added: 0006509                          
2023-10-03 11:59 kre            Note Added: 0006510                          
2023-10-03 12:11 kre            Note Added: 0006511                          
2023-10-03 13:42 geoffclare     Note Added: 0006512                          
2023-10-04 14:42 kre            Note Added: 0006513                          
2023-10-04 17:36 kre            Note Added: 0006514                          
2023-10-05 08:59 geoffclare     Note Added: 0006515                          
2023-10-05 11:08 kre            Note Added: 0006516                          
2023-10-05 14:53 geoffclare     Note Added: 0006517                          
2023-10-05 15:34 kre            Note Edited: 0006516                         
2023-10-05 15:35 kre            Note Edited: 0006516                         
2023-10-05 15:36 kre            Note Edited: 0006516                         
2023-10-05 15:38 kre            Note Added: 0006519                          
2023-10-05 15:41 kre            Note Edited: 0006513                         
2023-10-06 07:58 geoffclare     Note Edited: 0006515                         
2023-10-06 21:41 chet_ramey     Note Added: 0006524                          
2023-10-10 11:06 geoffclare     Note Edited: 0006515                         
2023-10-10 14:36 geoffclare     Note Added: 0006526                          
2023-10-10 17:19 kre            Note Added: 0006527                          
2023-10-11 08:04 geoffclare     Note Added: 0006528                          
2023-10-11 17:13 kre            Note Added: 0006529                          
2023-10-12 08:30 geoffclare     Note Added: 0006530                          
2023-10-12 18:33 kre            Note Added: 0006531                          
2023-10-12 18:45 kre            Note Edited: 0006516                         
2023-10-12 18:54 kre            Note Added: 0006532                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to