A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1804 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1804
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Resolved
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    sed 
Page Number:                3356, ff. 
Line Number:                114143, ff. 
Final Accepted Text:        https://austingroupbugs.net/view.php?id=1804#c6694 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2024-01-27 04:47 UTC
Last Modified:              2024-02-29 20:36 UTC
====================================================================== 
Summary:                    still some minor clarifications in the sed RE
description
====================================================================== 

---------------------------------------------------------------------- 
 (0006696) calestyo (reporter) - 2024-02-29 20:36
 https://austingroupbugs.net/view.php?id=1804#c6696 
---------------------------------------------------------------------- 
Looks good to me.

I assume it's by intention that in your changes to the y command there's no
direct mentioning of whether a literal <newline> is allowed (my original
point (3))?

I mean from "Any character other than <backslash> or <newline> can be used
instead of <slash> to delimit the strings." one can already deduce that
<newline> is a character and from "Replace all occurrences of characters in
string1 with the corresponding characters in string2." one could then
follow that is should therefore be allowed.

It may just be confusing that then there's still the <backslash>n escape
sequence (in addition). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-01-27 04:47 calestyo       New Issue                                    
2024-01-27 04:47 calestyo       Name                      => Christoph Anton
Mitterer
2024-01-27 04:47 calestyo       Section                   => sed             
2024-01-27 04:47 calestyo       Page Number               => 3356, ff.       
2024-01-27 04:47 calestyo       Line Number               => 114143, ff.     
2024-02-29 16:59 geoffclare     Note Added: 0006694                          
2024-02-29 17:00 geoffclare     Final Accepted Text       =>
https://austingroupbugs.net/view.php?id=1804#c6694    
2024-02-29 17:00 geoffclare     Status                   New => Resolved     
2024-02-29 17:00 geoffclare     Resolution               Open => Accepted As
Marked
2024-02-29 17:01 geoffclare     Tag Attached: tc1-2024                       
2024-02-29 20:36 calestyo       Note Added: 0006696                          
======================================================================


  • [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

Reply via email to