A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1920 
====================================================================== 
Reported By:                stephane
Assigned To:                
====================================================================== 
Project:                    1003.1(2013)/Issue7+TC1
Issue ID:                   1920
Category:                   Shell and Utilities
Type:                       Omission
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Stephane Chazelas 
Organization:                
User Reference:              
Section:                    read utility, stdin section 
Page Number:                3321 
Line Number:                112915 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2025-04-21 07:16 UTC
Last Modified:              2025-04-24 12:18 UTC
====================================================================== 
Summary:                    read -d '' on invalid text without -r and IFS=
====================================================================== 

---------------------------------------------------------------------- 
 (0007150) stephane (reporter) - 2025-04-24 12:18
 https://www.austingroupbugs.net/view.php?id=1920#c7150 
---------------------------------------------------------------------- 
Wow, I see the field splitting section has changed dramatically between the 2018
and 2024 editions (seemingling as the result of
https://www.austingroupbugs.net/view.php?id=1560 which was about "clarify
wording of command substitution").

And by the look of it, no shell hasn't been updated to implement the new
behaviour yet.

With `IFS=mé` in my BIG5-HKSCS example above, POSIX now requires the input to
be split on either `0x88 0x6d` or `0x6d` byte sequences. Does the order matter
or should it look for the longest of those occurences?

For "read" specifically, for backslash processing, it may be worth clarifying
that when the spec says "backslash", it means the byte encoding of that
character, wherever it's found (including inside the encoding of other
characters) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-04-21 07:16 stephane       New Issue                                    
2025-04-21 07:30 stephane       Note Added: 0007139                          
2025-04-21 07:38 stephane       Note Edited: 0007139                         
2025-04-22 14:46 geoffclare     Note Added: 0007140                          
2025-04-22 15:20 hvd            Note Added: 0007141                          
2025-04-22 18:45 chet_ramey     Note Added: 0007142                          
2025-04-23 14:59 dwheeler       Note Added: 0007143                          
2025-04-23 16:47 stephane       Note Added: 0007144                          
2025-04-23 16:57 stephane       Note Added: 0007145                          
2025-04-23 19:53 dwheeler       Note Added: 0007146                          
2025-04-24 10:54 geoffclare     Note Added: 0007147                          
2025-04-24 10:55 geoffclare     Note Edited: 0007147                         
2025-04-24 11:00 geoffclare     Note Added: 0007148                          
2025-04-24 11:23 stephane       Note Added: 0007149                          
2025-04-24 12:18 stephane       Note Added: 0007150                          
======================================================================


  • [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
  • [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
  • [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
  • [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
    • Re: (... Stephane Chazelas via austin-group-l at The Open Group
    • Re: [... Hans Åberg via austin-group-l at The Open Group

Reply via email to