3 ms·
my major and minor complaints are, in order: tee does something very specific, it makes an unmodified copy into a file (one branch of the plumbing tee-joint) a
by fsckboy 2y ago
my major and minor complaints are, in order:
tee does something very specific, it makes an unmodified copy into a file (one branch of the plumbing tee-joint) as it passes the stream to stdout (the other branch); as opposed to sed or awk or even grep, et al, which modify the stream. How in hell is this inspired by tee which does not modify its inputs?
and who capitalizes Tee?
- iforgot22 2y agoBecause it writes to a file like tee.
- willswire 2y agoHN autocorrect that’s who! Haha
- varenc 2y agoAgreed. `tee` without any flags is essentially a no-op and doesn’t have much use, whereas teemoji does. This feels more like `nl` in the sense that it outputs its STDIN with something prepended. But with the additional support for splitting the stream, in which case its STDOUT is unmodified like tee. I still absolutely love this project. It’s inspired me to play around with CoreML.
- hatthew 2y agoYeah, I feel like this should have been implemented solely as a single-in/single-out stream modifier. Then if you want to output to both a file and stdout, you can `command | emojify | tee`, or `command | tee | emojify` if you want to keep the file clean. Or if you want to emojify without splitting the stream (which I suspect would be the most common use case) you don't have to worry about the tee aspect at all.