The following issue has been UPDATED.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
==
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
The following issue has been set as RELATED TO issue 0001556.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigne
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
===
The following issue has been RESOLVED.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned To:
=
The following issue has been set as RELATED TO issue 0001578.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigne
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigned
The following issue has been set as RELATED TO issue 0001662.
==
https://austingroupbugs.net/view.php?id=1550
==
Reported By:calestyo
Assigne
Date:Sat, 2 Apr 2022 19:47:44 +
From:Austin Group Bug Tracker
Message-ID:
| That indented paragraph of yours (in Note 0005775) should (if at all)
| only go to the Rationale, IMO.
That's fine.
| Cause for the purpose of the standard itself it's not really
On Sun, 2022-04-03 at 08:41 +0700, Robert Elz via austin-group-l at The
Open Group wrote:
> Actually there's no reason to forbid them, they simply do
> not work. Applications cannot expect them to work.
> That's all that needs to be said.
Well than let's not call it forbid, but - as already the
3 Nisan 2022 Pazar tarihinde Christoph Anton Mitterer via austin-group-l at
The Open Group yazdı:
>
> But many of those extensions made by implementations in areas where
> POSIX doesn't define things, cause IMO quite some trouble in practise.
>
Such as?
--
Oğuz
On Sun, 2022-04-03 at 05:51 +0300, Oğuz wrote:
> 3 Nisan 2022 Pazar tarihinde Christoph Anton Mitterer via austin-
> group-l at The Open Group yazdı:
> > But many of those extensions made by implementations in areas where
> > POSIX doesn't define things, cause IMO quite some trouble in
> > practis
On Sat, Apr 2, 2022, at 11:34 PM, Christoph Anton Mitterer via austin-group-l
at The Open Group wrote:
> Apparently some sed implementations use \+ (and friends) in BREs like +
> EREs, while some use it as the literal + .
The behavior of things like \+ are explicitly undefined by the BRE
specific
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
>
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 wo
Robert Elz wrote, on 05 Apr 2022:
>
> | Okay, I'll see what I can do. It may make sense to use the new
> | definition of "escape sequence" from bug 1546.
>
> | It won't be possible in the y command, as that doesn't use an RE (so
> | would need its own definition of "escape character").
>
Date:Thu, 7 Apr 2022 10:37:06 +0100
From:"Geoff Clare via austin-group-l at The Open Group"
Message-ID: <20220407093706.GA7005@localhost>
| The new definition in bug 1546 is specific to regular expressions
| (since it talks about the backslash not being in a brac
Date:Thu, 07 Apr 2022 18:15:55 +0700
From:"Robert Elz via austin-group-l at The Open Group"
Message-ID: <5473.1649330...@jinx.noi.kre.to>
| | e.g. adding:
| |
| | For example, the context address "\.[.][0-9]." is equivalent
| | to "/\.[0-9]/".
On Tue, 2022-04-05 at 23:33 +0700, Robert Elz via austin-group-l at The
Open Group wrote:
> Not just portable, but sane. Only a moron would actually use . ? *
> [ ( ...
> as a delimiter, there are plenty of perfectly good alternatives
> available
> when good old / isn't the best choice (which it
On Tue, 2022-04-05 at 15:54 +0100, Geoff Clare via austin-group-l at
The Open Group wrote:
> > ---
> > ---
> > (0005771) calestyo (reporter) - 2022-04-02 01:53
> > https://austingroupbugs.net/view.php?id=1550#c5771
> >
Christoph Anton Mitterer wrote, on 18 Apr 2022:
>
> On Tue, 2022-04-05 at 15:54 +0100, Geoff Clare via austin-group-l at
> The Open Group wrote:
> > > ---
> > > ---
> > > (0005771) calestyo (reporter) - 2022-04-02 01:53
> > > https:
On Thu, 2022-04-21 at 15:10 +0100, Geoff Clare via austin-group-l at
The Open Group wrote:
> > >
> > > does not work, because if it appears unescaped later
> > > in
> > > the RE, it either escapes the following character, which can then
> > > never be the ending delimiter
> >
> > It feels a bit
Christoph Anton Mitterer wrote, on 26 Apr 2022:
>
> There's the thing left with e.g. GNU sed per default allowing escape
> sequences in bracket expressions,... but you already have the changes
> from #1233, and I guess there's not much more one can do about this
> situation.
> Perhaps finding out,
31 matches
Mail list logo