[Issue 8 drafts 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters)

2022-04-05 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1551 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001575]: imrpove indication that [^] as a bracket expression is not valid

2022-04-05 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been SUBMITTED. == https://austingroupbugs.net/view.php?id=1575 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

2022-04-05 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001575]: imrpove indication that [^] as a bracket expression is not valid

2022-04-05 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1575 == Reported By:calestyo Assigned To:

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

2022-04-05 Thread Robert Elz via austin-group-l at The Open Group
Date:Tue, 5 Apr 2022 15:54:40 +0100 From:"Geoff Clare via austin-group-l at The Open Group" Message-ID: <20220405145440.GB6489@localhost> | Okay, I'll see what I can do. It may make sense to use the new | definition of "escape sequence" from bug 1546. | It

Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

2022-04-05 Thread Geoff Clare via austin-group-l at The Open Group
Robert Elz wrote, on 05 Apr 2022: > > | > > An escape sequence is defined as the escape character followed > | > > by any single character. The escape character is a > | > > that is neither in a bracket expression nor itself escaped. > > | Okay, I'll propose that wording in Thursday's

Re: [Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

2022-04-05 Thread Geoff Clare via austin-group-l at The Open Group
Replying to a whole bunch of bugnotes here, including two from 1551. Together they are very long, so I've only quoted the minimum necessary to give context to my replies. > -- > (0005771) calestyo (reporter) - 2022-04-02 01:53

Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

2022-04-05 Thread Robert Elz via austin-group-l at The Open Group
Date:Tue, 5 Apr 2022 09:41:26 +0100 From:"Geoff Clare via austin-group-l at The Open Group" Message-ID: <20220405084126.GA6489@localhost> | > > ��� An escape sequence is defined as the escape character followed | > > ��� by any single character.� The escape

Re: [1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

2022-04-05 Thread Geoff Clare via austin-group-l at The Open Group
Christoph Anton Mitterer wrote, on 05 Apr 2022: > > > or it could be split into two sentences along the lines of your > > original > > suggestion: > > > >     An escape sequence is defined as the escape character followed > >     by any single character.  The escape character is a > >     that