Re: Odd bash behaviour with time:

[Eduardo A . Bustamante López]

To Piotr:

On Sat, Nov 01, 2014 at 12:35:47AM +0100, Piotr Grzybowski wrote:
>  well, thats what I have been trying to say, before Eduardo almost killed me 
> :)
>  help time clearly states that is requires a pipeline, NULL pipeline
> is something that does not exist. it is just a bad usage of time
> built-in.
Can you cut the crap? It's you not understanding the question and
pretending that you do. Also, don't send mail to me privately.

I don't take back the condescending part, because that's what you're doing,
pretending that you know more than the OP and I, without even actually
researching what's being discussed. It would be better if you just stepped
back, and waited for Chet's reply, who is the only one who has something
interesting to say about this.

Also, quit the broken Spanish and the references to killing. That's very
distasteful.


Evidently, you haven't read the manual:

| When the shell is in posix mode, time may be followed by a newline.  In this 
case, the shell displays the
| total user and system time consumed by the shell and its children.  The 
TIMEFORMAT variable may  be  used
| to specify the format of the time information.

That is: time\n

Hint: it's not followed by a pipeline.

It doesn't say about bash not running in posix mode, but, I'd expect that to be
the same behavior.



To jon:

> > 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.
I agree, if

  time

doesn't generate an error, why

  time; command

does...


That's a question for Chet to answer, or by someone that understands
what the parser is doing here.