A way around this would be to redirect the program output to a file, and then use 'tail -f logfile' to actually display it in screen.  If you enter copy mode, it would stop the tail -f, not the running program.  Command line could look like this:
    myprogram > logfile & tail -f logfile


Rogers Colin M wrote:

I'm running a program in that produces significant amounts of terminal output. I start this program in a detached screen, and at some point later attach it. This presents me with a view of the output from the program, which is fine.

 

However, if I then enter copy mode, a short while later the program stops execution, and only resumes when I leave copy mode. This is very irritating as the program is time dependent, and so stopping it running causes problems.

 

I can't find anything about this in the manual, so can anyone tell me if this is the intended behaviour, and whether I can get around it in anyway (i.e. allow the program to keep outputting to the "terminal" when in copy mode?)

 

TIA


_______________________________________________
screen-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/screen-users

Reply via email to