In windows vista (only platform I tested on), when you send a message to [popen], the output from the first outlet has an unpredictable behaviour.
Here's some of the things that happen (same test gives different results if repeated):
1) The expected output, i.e. the output generated by the command in the "shell", one symbol ber line
2) "sending <message>" where <message> is a verbatim copy of the message you have input
3) "sending <message><junk>" where <junk> is either a random sequence of unreadable characters, or a random slice of some previously input message
4) When the output of the command is mulltiline (e.g. "dir") you sometimes get only the first N lines (correctly output as multiple symbol messages, but not all the messages that the command actually produces in the shell, e.g. in the case of "dir" not the complete list of files)
These are the cases I've been able to observe.
By the way by "expected behaviour" I mean what I guess is the expected behaviour, as the help-patch totally lacks a description of what the external does.
Anonymous
can you tell me whether this is flatspace/popen or moonlib/popen?