Very Computer

I wonder if this was possible : in my script, I launch many processes in
background and I'd like to see the output in different terminals.

example:
for file in $files; do
   #launch xterm
   my_prog $file > to_the_new_xterm &
done

Do you have other ideas ? How can I do this ?

Thanks a lot.

Fred

Quote:> example:
> for file in $files; do
>    #launch xterm
>    my_prog $file > to_the_new_xterm &
> done

> Do you have other ideas ? How can I do this ?

The idea is that you have a process running in the current shell, and it
generates various bits of terminal output that you don't want to lose (have
vanish), but then you reach a point where a particular piece of the process
generates a lot of output such that you would ordinarily run it through
a pager.  But the problem is that the pager takes over the screen and
blasts away the previous contents (*).  So, what I do is (something like):

mkfifo /tmp/apipe
xterm -e less -f /tmp/apipe &
...
someprocess > /tmp/apipe
...

You might want to try something like this.

(*) Yes, I knew that some terminal types address this by having an
"alternate screen", but that doesn't always work and doesn't fully solve
the issue (when it does work).

Quote:> mkfifo /tmp/apipe
> xterm -e less -f /tmp/apipe &
> ...
> someprocess > /tmp/apipe

Note that you can avoid the named pipe by using an unnamed one
and a fd above 2:

someprocess | xterm -e sh -c 'less <&3' 3<&0

--
Stphane                      ["Stephane.Chazelas" at "free.fr"]

Quote:> (*) Yes, I knew that some terminal types address this by having an
> "alternate screen", but that doesn't always work and doesn't fully solve
> the issue (when it does work).

--
Stphane                      ["Stephane.Chazelas" at "free.fr"]

Quote:>2004-02-06, 15:41(+00), Kenny McCormack:
>[...]
>> mkfifo /tmp/apipe
>> xterm -e less -f /tmp/apipe &
>> ...
>> someprocess > /tmp/apipe
>[...]

>Note that you can avoid the named pipe by using an unnamed one
>and a fd above 2:

>someprocess | xterm -e sh -c 'less <&3' 3<&0

Quote:>>> mkfifo /tmp/apipe
>>> xterm -e less -f /tmp/apipe &
>>> ...
>>> someprocess > /tmp/apipe
>>[...]

>>Note that you can avoid the named pipe by using an unnamed one
>>and a fd above 2:

>>someprocess | xterm -e sh -c 'less <&3' 3<&0

> Nope.

Here it works with xterm XFree86 4.3.99.15(180).

--
Stphane                      ["Stephane.Chazelas" at "free.fr"]

Quote:>2004-02-06, 16:48(+00), Kenny McCormack:
>[...]
>>>> mkfifo /tmp/apipe
>>>> xterm -e less -f /tmp/apipe &
>>>> ...
>>>> someprocess > /tmp/apipe
>>>[...]

>>>Note that you can avoid the named pipe by using an unnamed one
>>>and a fd above 2:

>>>someprocess | xterm -e sh -c 'less <&3' 3<&0

>> Nope.

>Which version of xterm is it? Does your version of xterm close
>every fd (before assigning 0, 1 and 2 and starting less)? Does
>someprocess get a SIGPIPE?

>Here it works with xterm XFree86 4.3.99.15(180).

Quote:>>>>> mkfifo /tmp/apipe
>>>>> xterm -e less -f /tmp/apipe &
>>>>> ...
>>>>> someprocess > /tmp/apipe
>>>>[...]

>>>>Note that you can avoid the named pipe by using an unnamed one
>>>>and a fd above 2:

>>>>someprocess | xterm -e sh -c 'less <&3' 3<&0
[...]
>>Here it works with xterm XFree86 4.3.99.15(180).

> To quote Willy boy Clinton, "It depends on what the meaning of the word
> 'works' is."

With my version of xterm

mkfifo /tmp/apipe
xterm -e less -f /tmp/apipe &
someprocess > /tmp/apipe

and

someprocess | xterm -e sh -c 'exec less <&3' 3<&0

work exactly the same (except for the shell message for the job
being run in background, and the (unwanted) fifo created in /tmp
[probably with world reading permissions]).
That's all and I'm not going to try any harder to guess what you
exactly meant by "Nope".

--
Stphane                      ["Stephane.Chazelas" at "free.fr"]

Quote:>2004-02-06, 16:48(+00), Kenny McCormack:
>[...]
>>>> mkfifo /tmp/apipe
>>>> xterm -e less -f /tmp/apipe &
>>>> ...
>>>> someprocess > /tmp/apipe
>>>[...]

>>>Note that you can avoid the named pipe by using an unnamed one
>>>and a fd above 2:

>>>someprocess | xterm -e sh -c 'less <&3' 3<&0

>> Nope.

>Which version of xterm is it? Does your version of xterm close
>every fd (before assigning 0, 1 and 2 and starting less)? Does
>someprocess get a SIGPIPE?

>Here it works with xterm XFree86 4.3.99.15(180).

Quote:>>>>someprocess | xterm -e sh -c 'less <&3' 3<&0
[...]
> Actually, I just got around to testing this some more today, and found that
> it does indeed work (on Solaris) with xterm, but not with rxvt.  rxvt seems
> to be broken in this regard.  rxvt is my preferred "xterm work-alike".

--
Stphane                      ["Stephane.Chazelas" at "free.fr"]