A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1532 
====================================================================== 
Reported By:                stephane
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1532
Category:                   Shell and Utilities
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Stephane Chazelas 
Organization:                
User Reference:             https://austingroupbugs.net/view.php?id=1053 
Section:                    stty utility 
Page Number:                 
Line Number:                 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2021-11-03 14:15 UTC
Last Modified:              2021-11-03 14:51 UTC
====================================================================== 
Summary:                    "stty -g" output should not have to be split
====================================================================== 

---------------------------------------------------------------------- 
 (0005514) stephane (reporter) - 2021-11-03 14:51
 https://austingroupbugs.net/view.php?id=1532#c5514 
---------------------------------------------------------------------- 
> The reference to 2.6 suggests maybe "sh" should be involved to
> perform that splitting. It almost suggests that the output
> should be appended to "stty ", or possibly "stty -- " and fed to
> sh as in (printf "stty -- "; stty -g) | sh

That however wouldn't work as sh's stdin would then be a pipe and not the
terminal . Not to mention the fact that if stty -g fails, the code becomes
"stty " or "stty --" which requests tty settings.

Also, in:

> The form used shall
> consist of one line of text consisting of only printable
> characters from the portable character set, excluding
> whitespace characters, NUL, and all characters that are
> special in the syntax of the sh language
> (`"$&*()[]{};'#~?<>\|).

Since I've added "printable" (with the intention of excluding control
characters), the "NUL, " is redundant. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2021-11-03 14:15 stephane       New Issue                                    
2021-11-03 14:15 stephane       Name                      => Stephane Chazelas
2021-11-03 14:15 stephane       User Reference            =>
https://austingroupbugs.net/view.php?id=1053      
2021-11-03 14:15 stephane       Section                   => stty utility    
2021-11-03 14:23 stephane       Note Added: 0005513                          
2021-11-03 14:51 stephane       Note Added: 0005514                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
      • Re:... Wayne Pollock via austin-group-l at The Open Group
        • ... Don Cragun via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to