time is *not* working as documented. This has been reported twice here
on Launchpad and at least once on Debian.
Here's how I got bitten by the bug:
1. I've used "time ./program" to time single runs before. I wanted to get
memory usage information this time.
2. I executed "man time" to find out about its options.
3. I ran "time" in accordance with those options. It then gave me a confusing
error message, and I was about to file a bug when I found this report and
understood what was going on. (The memory usage options don't work anyway, but
that's not really the point.)
Where did I go wrong? I'm not the only person to have been bitten by
this, so there's clearly something wrong. Whether the man page should be
for the bash builtin, or some other solution, the current situation is
unintuitive, if not flat-out misleading, and this report will keep
getting duplicated because users will go through the same steps that I
did and end up scratching their heads in the same way that I did.
** Changed in: time (Ubuntu)
Status: Rejected => Confirmed
--
hoary: Time sees every argument as a program to run.
https://launchpad.net/bugs/14172
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
