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

2022-10-31 Thread Christoph Anton Mitterer via austin-group-l at The Open Group
Hey folks. A while ago we had this discussion about pattern matching notation and characters vs. bytes. Back then, Harald von Dijk did some investigation on whether the standard could be changed to allow for bytes (and not just characters) without breaking all kinds of shells. IIRC, when he

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Robert Elz via austin-group-l at The Open Group
Date:Mon, 31 Oct 2022 19:03:53 + From:"Stephane Chazelas via austin-group-l at The Open Group" Message-ID: <20221031190353.ar33l2s6dwkor...@chazelas.org> | [ is perfectly fine after we deprecate -a, -o binary operators | and "(", ")". Which was done ages

Re: [Issue 8 drafts 0001611]: exit status from fg is either badly specified or is simply wrong

2022-10-31 Thread Robert Elz via austin-group-l at The Open Group
Date:Mon, 31 Oct 2022 16:39:06 + From:Austin Group Bug Tracker Message-ID: | This is already being fixed by bug | https://austingroupbugs.net/view.php?id=1254, OK, thanks, that is fine. If I trusted my ability to conduct a search in mantis, I might

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Stephane Chazelas via austin-group-l at The Open Group
2022-10-31 12:00:24 -0700, Scott Lurndal via austin-group-l at The Open Group: [...] > However, another benefit of the '[[' builtin is that it does not > do word splitting or pattern expansion. [...] "[" doesn't do word splitting of pathname expansion either, it's the shell that does if you

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Stephane Chazelas via austin-group-l at The Open Group
2022-10-31 10:35:38 -0700, Scott Lurndal via austin-group-l at The Open Group: [...] > Historically, '[[' was implemented directly by the shell, while '[' > was implemented using fork(), exec("[").There is clearly a benefit > to eliminating process creation. [...] AFAIK and as also suggested

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Scott Lurndal via austin-group-l at The Open Group
On Mon, Oct 31, 2022 at 11:24:06AM -0700, Roger Marquis wrote: > scott wrote: > >Historically, '[[' was implemented directly by the shell, while '[' > >was implemented using fork(), exec("[").There is clearly a benefit > >to eliminating process creation. > > Isn't that an implementation

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Tapani Tarvainen via austin-group-l at The Open Group
On Mon, Oct 31, 2022 at 11:24:06AM -0700, Roger Marquis via austin-group-l at The Open Group (austin-group-l@opengroup.org) wrote: > Korn shell does predate Perl by 4 years (according to > Wikipedia). Was the operator in question part of the initial > implementation though (David)? The [[ ...

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Roger Marquis via austin-group-l at The Open Group
scott wrote: Historically, '[[' was implemented directly by the shell, while '[' was implemented using fork(), exec("[").There is clearly a benefit to eliminating process creation. Isn't that an implementation detail that can be easily changed? If so not sure it'd be relevant to the

Re: [1003.1(2008)/Issue 7 0000375]: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef

2022-10-31 Thread Scott Lurndal via austin-group-l at The Open Group
On Sun, Oct 30, 2022 at 02:06:48PM -0700, Roger Marquis via austin-group-l at The Open Group wrote: > >Now i read stephane's "MO, [[...]] has no benefit other than cosmetic over > >[" (#5973) > > No benefit is key, but the cost is also an issue, cost in terms of > compatibility. Historically,

[1003.1(2016/18)/Issue7+TC2 0001254]: "asynchronous list" description uses "command" instead of "AND-OR list"

2022-10-31 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The issue 0001611 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=1254 == Reported By:stephane

[Issue 8 drafts 0001611]: exit status from fg is either badly specified or is simply wrong

2022-10-31 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been set as DUPLICATE OF issue 0001254. == https://austingroupbugs.net/view.php?id=1611 == Reported By:kre Assigned

[Issue 8 drafts 0001611]: exit status from fg is either badly specified or is simply wrong

2022-10-31 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=1611 == Reported By:kre Assigned To:

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

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

[Issue 8 drafts 0001561]: clarify what kind of data shell variables need to be able to hold

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

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

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

[1003.1(2016/18)/Issue7+TC2 0001585]: kill - add -j option to avoid PID reuse race

2022-10-31 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been CLOSED. == https://austingroupbugs.net/view.php?id=1585 == Reported By:steffen Assigned To:

[Issue 8 drafts 0001591]: Proposed strlcpy spec has problems

2022-10-31 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been CLOSED. == https://austingroupbugs.net/view.php?id=1591 == Reported By:eggert Assigned To: