It could also be interesting to kill the process from pd. A bit of kill scripting is easy.<div><br></div><div>About implementing, I can try to sketch something out.. but nothing earlier than the 16th... I have a deliverable to get ready until then! :(</div>
<div><br></div><div><br></div><div>Best regards,</div><div>Pedro<br><br><div class="gmail_quote">On Fri, Jul 2, 2010 at 9:42 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at">hans@at.or.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On Jul 2, 2010, at 3:47 AM, Pedro Lopes wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> #!/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>
</blockquote>
<br>
<br></div>
Want to implement it? :-D The status outlet would give you info like the name of the process running, whether its still running, etc.<br>
<br>
.hc<br>
<br>
<br>
<br>
<br>
----------------------------------------------------------------------------<br>
<br>
Programs should be written for people to read, and only incidentally for machines to execute.<br>
- from Structure and Interpretation of Computer Programs<br>
<br>
</blockquote></div><br><br clear="all"><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>
</div>