Hi Daniel (@greenembrace),
I was wondering who would be the first one to ask this question. When I got the idea to provide a Terminal-Input node, then of course I got the same idea to:
- Build a Terminal-Output node
- Add an output on the Terminal-Input node
Unfortunately I didn't found a solution for none of both 
Therefore I have explained it in more detail in the Limitations section of my readme page.
Summarized:
Suppose you have N users each having their own flow editor open at the same time. Then each Terminal-Input in the flow will be displayed N times, but on the server it is a single node. Suppose I add an output to the Terminal-Input node:
- User 1 the button, and expects his working directory to appear on the output.
- Meanwhile user 2 presses the output, and expects his working directory to appear on the output
- The output always shows a mixed output of both users
But while I'm writing this now, I'm realizing that the Inject node has the same problem. Damn how stupid of me
Any thoughts from the community???
P.S. A Terminal-Output node would be harder to develop. You will get the output from all users, but on top of that you will also get the input of all users. Because the output of the pseudo terminal contains both (input and output). For a Terminal-Input node, I know both the input and output so I can remove the input from the stream. For an Terminal-Output node this would be much more difficult, and I don't have spare time left for such features...
