query: xargs: 'ls' terminated by signal 13
positive_passages.docid: 151037
positive_passages.text: limit find output AND avoid signal 13
negative_passages.docid: 52340
negative_passages.text: "-bash: ls: command not found"
negative_passages.docid: 84015
negative_passages.text: \leqslant causes "Undefined control sequence"
negative_passages.docid: 17384
negative_passages.text: Output from ls has newlines but displays on a single line. Why?
negative_passages.docid: 100667
negative_passages.text: Providing/passing argument to signal handler
negative_passages.docid: 55961
negative_passages.text: Why doesn't my loop over the output of ls work?
negative_passages.docid: 22136
negative_passages.text: How can I protect parentheses passed to a cd command?
negative_passages.docid: 10354
negative_passages.text: Why *not* parse `ls` (and what to do instead)?
negative_passages.docid: 44772
negative_passages.text: Why `ls -d` only demonstrate `.`?
negative_passages.docid: 124285
negative_passages.text: Python interpreter error, x takes no arguments (1 given)
negative_passages.docid: 63797
negative_passages.text: dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) nginx
negative_passages.docid: 9449
negative_passages.text: ls command: what does the first line mean?
negative_passages.docid: 102251
negative_passages.text: '\r' added end of the script command
negative_passages.docid: 58140
negative_passages.text: Why can lstlisting not be saved in a command?
negative_passages.docid: 142255
negative_passages.text: How can I direct a pipe input to ls command?
negative_passages.docid: 8811
negative_passages.text: The issue of * in Command line argument
negative_passages.docid: 135121
negative_passages.text: Why doesn't the command "ls | file" work?