Re: [1003.1(2004)/Issue 6 0000267]: time (keyword)

2020-02-19 Thread Geoff Clare
Robert Elz wrote, on 18 Feb 2020: > > Date:Mon, 17 Feb 2020 15:22:08 + > From:Geoff Clare > > | Not at all. If the discrepancy between ksh88 and POSIX.2-1992 had > | come to light before those systems were certified, the standard would > | have been amended to

[1003.1(2016)/Issue7+TC2 0001300]: clarify GLOB_MARK behavior

2020-02-19 Thread Austin Group Bug Tracker
The following issue has been UPDATED. == https://www.austingroupbugs.net/view.php?id=1300 == Reported By:dmitry_goncharov Assigned To:

[1003.1(2016)/Issue7+TC2 0001306]: Documented folder= behaviour contradicts implementations (of folders command)

2020-02-19 Thread Austin Group Bug Tracker
The following issue has been UPDATED. == https://www.austingroupbugs.net/view.php?id=1306 == Reported By:steffen Assigned To:

Re: [1003.1(2004)/Issue 6 0000267]: time (keyword)

2020-02-19 Thread Joerg Schilling
Stephane Chazelas wrote: > Note that AT ksh and bosh revert to calling the standalone > time utility in that case so they can't be used to time > builtin/functions. Well, if you enforce to implement the old POSIX behavior, you get what the old POSIX definition says: timing is only possible for

Re: [1003.1(2004)/Issue 6 0000267]: time (keyword)

2020-02-19 Thread Stephane CHAZELAS
2020-02-19 11:52:21 +0100, Joerg Schilling: [...] > > $ zsh -c 'time -p uname | cat' > > zsh:1: command not found: -p > > BTW: I remember that you frequently write that zsh intends to emulate the csh > behavior, but csh _is_ able to get timing for builtin commands: > > csh > % time alias > 0.0u