> #!/bin/bash<br>> echo "this goes to stdout"<br>> echo "this goes to stderr" 1>&2<br>>(Which should have been obvious from the familiar "pd -stderr 2>&1")<br><br>
Yep I use a similar trick in UNIX find, like trying to find .pd files:<br>- find / -name "*.pd*" -type f -print 2>/dev/null<br><br><br>>I am thinking of the ideal version of this, an object that would give
you an inlet for STDIN then two >outlets for STDOUT and STDERR, plus a
status outlet and an inlet to set what to run. It could be >something
like this:<br>
<br>>[process /usr/bin/python]<br>
<br>>Then you could send python bits to it via the first inlet, and receive
the reply via the outlets. So >something like a cleaner [shell].<br><br>NIce hc. That's an interesting object, sending messages in a simple way to a shell process running in the background should be fairly easy. Just didn't get what you mean by status outlet..<br>
<br>best regards,<br>Pedro<br>-- <br>Pedro Lopes<br>contacto: <a href="mailto:jazz@radiozero.pt">jazz@radiozero.pt</a><br>website: <a href="http://web.ist.utl.pt/Pedro.Lopes">http://web.ist.utl.pt/Pedro.Lopes</a> <br>