Timeline for time printing its output before the command it runs
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2019 at 9:47 | comment | added | muru | In that case, consider using that option anyway, and using cat on that file after the command completes. | |
| Aug 2, 2019 at 9:36 | comment | added | Tom Anderson | @muru Yes, it's just me reading it! And that is much easier if the time output is in a consistent place. | |
| Aug 1, 2019 at 22:04 | answer | added | Rey Estrada | timeline score: -1 | |
| Aug 1, 2019 at 18:13 | comment | added | muru | Then "interpretation of the log" is just human interpretation? | |
| Aug 1, 2019 at 16:13 | comment | added | Tom Anderson | @muru I don't want to parse time's output. | |
| Aug 1, 2019 at 12:58 | comment | added | muru | Buffering, yes. If you're really looking to parse time's output, why aren't you using its option for saving output to a file (-o, IIRC)? | |
| Aug 1, 2019 at 12:54 | history | asked | Tom Anderson | CC BY-SA 4.0 |