Re: [MLUG] Passing options to the time command

[Stephen Montgomery-Smith <EMAIL:PROTECTED>]

Jonathan King wrote:
> On 11/3/07, Adam Procter <EMAIL:PROTECTED> wrote:
> >  Right, but observe:
> >
> >
> >  [EMAIL:PROTECTED ~]$ /usr/bin/time -V
> >  GNU time 1.7
> >
> >  [EMAIL:PROTECTED ~]$ time -V
> >  -V: Command not found.
> >  0.000u 0.000s 0:00.00 0.0%      0+0k 0+0io 0pf+0w
> >
> >  If you don't supply the full path, bash will use its built-in version of
> > the command, which is less featureful (or doesn't support the -V flag, in
> > any case).
>
> Ooh! One of my pet peeves! I hate it when I can do this:
>
> $ which time
> /usr/bin/time
> $ time -V
> -bash: -V: command not found
>
> EMAIL:PROTECTED bash!
>
> I really think bash should have "which" as a built-in, so it can tell
> you when it's hosing you over and maybe do this:
>
> $ which time
> /usr/bin/time shadowed by bash function "time"
>
> There's another situation I run into that's similarly annoying, but I
> guess it's too late for me to remember what it is...

This is one place where tcsh is better than bash!

%which time
time: shell built-in command.

I actually assumed this would be true in bash.  This partially explains 
my earlier misinformation (for which I apologize).


_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members