[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-time] on OSX gtime prints to stderr, not stdout, unlike what do
From: |
Assaf Gordon |
Subject: |
Re: [Bug-time] on OSX gtime prints to stderr, not stdout, unlike what docs says |
Date: |
Wed, 7 Mar 2018 00:37:27 -0700 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
Hello,
On Wed, Jan 31, 2018 at 08:08:38PM -0800, Timothee Cour wrote:
> -o, --output=FILE write to FILE instead of STDOUT
> hilite gtime -v echo foo
> shows the gtime's output in red, so stderr
Thank you for reporting this issue.
Now fixed in:
https://git.savannah.gnu.org/cgit/time.git/commit/?id=b70627a9
> also, formatting is bad, missing spaces:
>
> gtime echo foo
> foo
> 0.00user 0.00system 0:00.00elapsed 66%CPU (0avgtext+0avgdata 820maxresident)k
> 0inputs+0outputs (1major+334minor)pagefaults 0swaps
While I agree that this output is less than optimal,
it has been the same for at least 21 years.
Changing it now will break a long held format and might break
existing scripts.
However,
Any desired format can be specified with "--format",
there is an "--verbose" option to output all information
in a more readable way,
and I'm also happy to learn about other formats that are
commonly used, and add a short option for it.
regards,
- assaf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Bug-time] on OSX gtime prints to stderr, not stdout, unlike what docs says,
Assaf Gordon <=