Hello,
Dear Eduardo. I am really sorry that you felt offended. I sent you a
private mail in order keep the list clean, and to show that there are
no hard feelings, sorry if you felt offended by that as well. Just in
passing my Spanish is not broken, and sorry if you felt offended by
that too.
Pl
On 10/31/14 2:01 PM, b...@m8y.org wrote:
> $ time;
>
> real0m0.000s
> user0m0.000s
> sys 0m0.000s
> $ time;ls
> bash: syntax error near unexpected token `ls'
> $ /usr/bin/time;/bin/ls Usage: /usr/bin/time [-apvV] [-f format] [-o file]
> [--append] [--verbose]
>[--portability] [
Hi Chet, hi all.
based on what you say, and some comments in parse.y ;-) isn't the
below patch enough to get rid of the parser error for "time;echo;"
case?
diff --git a/parse.y b/parse.y
index 815db98..766f258 100644
--- a/parse.y
+++ b/parse.y
@@ -1224,6 +1224,8 @@ pipeline_command: pipeline
Piotr Grzybowski wrote:
This is not meaningful:
# time ;echo hello
bash: syntax error near unexpected token `echo'
Ahh...and this IS meaningful: (?)
# time ; ; echo hello
0.00sec 0.00usr 0.00sys (0.00% cpu)
hello
How about this?
# time ; ; sleep 1
or this?
# time ; ; time sleep 1
0.00sec
On 11/1/14 2:10 PM, Piotr Grzybowski wrote:
> Hi Chet, hi all.
>
> based on what you say, and some comments in parse.y ;-) isn't the
> below patch enough to get rid of the parser error for "time;echo;"
> case?
Yes, it's probably the right thing to do for maximum compatibility with
the external `
