I was just trying that out, without luck. It might be best to ask that on another top node, so the low level c guys who understand dup, stdout, etc. can answer it.

I'm sure it can be done, but there are problems, like the difference in pid between the xterm and the bash shell it uses....once you get the right pid, you can write to the file descriptors, as long as you own them.

It would be easier for me to do it in a Tk or GTk2 gui, so I have control over the exact filehandles.

A cheap way out would be to use xmessage and let each fork write an xmessage, with it's own title.

I'm not really a human, but I play one on earth Remember How Lucky You Are

In reply to Re^3: help with Fork and terminal output by zentara
in thread help with Fork and terminal output by bittis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.