[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Odd bash behaviour with time:
From: |
jon |
Subject: |
Re: Odd bash behaviour with time: |
Date: |
Fri, 31 Oct 2014 23:31:12 +0000 |
On Fri, 2014-10-31 at 15:56 -0700, Eduardo A. Bustamante López wrote:
> > well, help time clearly states how it should be used.
> You are clearly not understanding the point.
>
> The point is: why does
>
> time
>
> work, but
>
> time ; somecommand
>
> doesn't.
>
> It's that simple. It's not a usage question, I'm very aware of how to
> use time. Stop being condescending.
Interesting interpreter question, but does "time" on its own have any
meaning? - if not "time" with no arguments should generate an error
rather than an output as it does currently.
This is meaningful
# time /bin/bash -c 'sleep 1' ;echo hello
real 0m1.003s
user 0m0.004s
sys 0m0.000s
hello
This is not
# time ;echo hello
bash: syntax error near unexpected token `echo'
- Odd bash behaviour with time:, bugs, 2014/10/31
- Re: Odd bash behaviour with time:, Piotr Grzybowski, 2014/10/31
- Re: Odd bash behaviour with time:, Eduardo A . Bustamante López, 2014/10/31
- Re: Odd bash behaviour with time:, Piotr Grzybowski, 2014/10/31
- Re: Odd bash behaviour with time:, Eduardo A . Bustamante López, 2014/10/31
- Re: Odd bash behaviour with time:,
jon <=
- Re: Odd bash behaviour with time:, Piotr Grzybowski, 2014/10/31
- Re: Odd bash behaviour with time:, Eduardo A . Bustamante López, 2014/10/31
- Re: Odd bash behaviour with time:, jon, 2014/10/31
- Re: Odd bash behaviour with time:, Ryan Cunningham, 2014/10/31
- Re: Odd bash behaviour with time:, Ryan Cunningham, 2014/10/31
- Re: Odd bash behaviour with time:, Eduardo A . Bustamante López, 2014/10/31
- Re: Odd bash behaviour with time:, Piotr Grzybowski, 2014/10/31