Re: [Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

On Fri, 2022-04-15 at 00:44 +0100, Harald van Dijk via austin-group-l at The Open Group wrote: > Hmm, I would. I like that :-D This would have been the preferred alternative I've asked for to look at, in the ticket. > Shells > are not in agreement on whether such single bytes can be matched

Re: [Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

On Tue, 2022-04-12 at 18:54 +0700, Robert Elz via austin-group-l at The Open Group wrote: > The point was that, at least as I read the proposed text, you're > defining > things like '*' to only work (reliably as specified) when the locale > is > POSIX (aka C).   In the user's locale, who knows

[Issue 8 drafts 0001562]: printf utility: clarify what is (byte) string an what is character string

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1562 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1564 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1564 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001544]: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1544 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001560]: clarify wording of command substitution

A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1560 == Reported By:calestyo Assigned To:

Re: [Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

Date:Thu, 14 Apr 2022 09:42:37 +0100 From:"Geoff Clare via austin-group-l at The Open Group" Message-ID: <20220414084237.GA15370@localhost> | That is how things are at present. The suggested changes just make it | explicit. Yes, I know, but that's what I am

[1003.1(2016/18)/Issue7+TC2 0001563]: Wording for what seem to imply odd behavior. "all occurrences of @(#)"

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1563 == Reported By:andras_farkas Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001563]: Wording for what seem to imply odd behavior. "all occurrences of @(#)"

The following issue NEEDS AN INTERPRETATION. == https://austingroupbugs.net/view.php?id=1563 == Reported By:andras_farkas Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001563]: Wording for what seem to imply odd behavior. "all occurrences of @(#)"

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1563 == Reported By:andras_farkas Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001544]: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1544 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001544]: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1544 == Reported By:calestyo Assigned To:

Re: [Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

Robert Elz wrote, on 12 Apr 2022: > > | 1. The vast majority of apps will never need to do that because they know > | (or can assume) that the pathnames they handle either always use the > | portable filename character set or use the user's locale. > > The latter, perhaps, the former,