Timeline for How to measure time of program execution and store that inside a variable
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2017 at 6:38 | comment | added | Paul Pritchard |
Basile, you are quite right. I hadn't spotted the significance of the command command. Which is fact ensures that /usr/bin/time is called. This means that the following two statements are compatible: $ command time -f %e sleep 4 and $ /usr/bin/time -f %e sleep
|
|
| Sep 19, 2017 at 12:29 | comment | added | 0xC0000022L |
If you want to ensure you're running the command, use command, if you want to ensure you're running the builtin, use builtin. There's no magic here. Use help to figure out the commands available or type <command> to figure out what type <command> is (e.g. a builtin, external command, function or alias).
|
|
| Sep 19, 2017 at 11:57 | comment | added | Basile Starynkevitch |
time is also a builtin shell.
|
|
| Sep 19, 2017 at 11:38 | review | Late answers | |||
| Sep 19, 2017 at 11:45 | |||||
| Sep 19, 2017 at 11:22 | history | answered | Paul Pritchard | CC BY-SA 3.0 |