The reason 'enable' does not list the 'time' builtin is that in bash
'time' is a keyword, not a builtin. The reason is because
syntactically bash's 'time' governs an entire pipeline, not just a
single command. See the section "Pipelines" of the bash man page.
Besides using /usr/bin/time, you c
Unfortunately, it looks as if bash doesn't have a "time" builtin (only a
"times" one), so this is - at best - only part of the problem. But
still, this builtin seems to be the cause here.
Perhaps reassign the bug to bash (since it is impossible to disable the
builtin interpretation of "time" since
This is not a bug in the debian `time' program , but you get this
problem when you use Bash (or another shells) built-in time command.
Use /usr/bin/time and you will see that all works as expected.
Greetings,
Bas Kloet
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscr
Package: time
Version: 1.7-21
Severity: important
Time does not parse its own parameters and treats everything on the
command line like the program it should run and its parameters.
For example the following works:
[EMAIL PROTECTED]:~/tmp/randwrite$ time bash < /dev/null
real0m0.005s
us
4 matches
Mail list logo
