query: Piping commands, modify stdin write to stdout
positive_passages.docid: 150326
positive_passages.text: Get input from editor (vim/nano/emacs/textmate?)
negative_passages.docid: 138144
negative_passages.text: How to trick an application into thinking its stdout is a terminal, not a pipe
negative_passages.docid: 105115
negative_passages.text: Writing command output in Windows cmd to a file (with a twist)
negative_passages.docid: 81714
negative_passages.text: Piping STDERR vs. STDOUT
negative_passages.docid: 120003
negative_passages.text: How does pipe work in bash commands?
negative_passages.docid: 91672
negative_passages.text: Rerouting stdin and stdout from C
negative_passages.docid: 119739
negative_passages.text: Process substitution and cat: can't read stdin
negative_passages.docid: 69760
negative_passages.text: Correct location for piping and redirecting output in find -exec?
negative_passages.docid: 60864
negative_passages.text: Include command in output file?
negative_passages.docid: 136267
negative_passages.text: Pipe the output of a command if it is successful
negative_passages.docid: 20894
negative_passages.text: How do I pipe terminal standard output (stdout) to the clipboard?
negative_passages.docid: 47406
negative_passages.text: How to write console output to a txt file
negative_passages.docid: 62834
negative_passages.text: tee stdout to stderr?
negative_passages.docid: 36533
negative_passages.text: Redirect stdin and stdout to ports
negative_passages.docid: 131327
negative_passages.text: Redirect output from all commands to file, not just last
negative_passages.docid: 14304
negative_passages.text: Why does bash output data instead of executing, when a script is piped?
negative_passages.docid: 134030
negative_passages.text: Use the output of a command as input of the next command