Timeline for Best way to `tee` to stdout and to a process
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2020 at 18:27 | vote | accept | Alexander Mills | ||
| Oct 2, 2019 at 9:21 | comment | added | Stéphane Chazelas |
somecommand | tee >(othercommand); cmd3 is problematic in several shell implementations including bash in that othercommand is not waited for, so its output may come after the output of cmd3 for instance. { cmd1 3>&- | tee /dev/fd/4 4>&1 >&3 3>&- | cmd2 3>&-; } 3>&1 would not have the problem and would work with POSIX sh on systems with /dev/fd/x
|
|
| Oct 2, 2019 at 7:40 | history | edited | Kusalananda♦ | CC BY-SA 4.0 |
added 21 characters in body
|
| Sep 18, 2019 at 21:46 | history | edited | Kusalananda♦ | CC BY-SA 4.0 |
added 47 characters in body
|
| Sep 18, 2019 at 21:33 | history | edited | Kusalananda♦ | CC BY-SA 4.0 |
edited body
|
| Sep 18, 2019 at 21:27 | history | answered | Kusalananda♦ | CC BY-SA 4.0 |