Thanks for the suggestion. However it would have been nice if screen
could do this.
I would then be able to monitor commands I hadn't anticipated the need for
monitoring when I started the command.
If I were to try to patch such a thing on to screen, where should I
start? I can see
screen.c '
One way might be to pipe the program's output through 'grep.' If you want to
see the full output also, you could do something hackish like:
mknod foo p
program | tee foo
screen grep pattern foo
Then set screen's activity monitor on the newly opened screen containing the
grep output.
--Joe
-
Hi,
I want to make screen look for a certain configurable pattern in the
output to detect "activity" (for the montoring feature
Cntrl-a M thingy). I am running a custom program which would print a
certain pattern that I want to watch for, not
necessarily a strict "silence" or "activity"- which
Bonjour Stéphane,
On Tuesday, May 9, 2006 at 8:05:43 +0100, Stéphane Chazelas wrote:
> Here is what I have. This is screen entry with some xterm specific
> keys and features added (note that the name "screen.xterm-256color" is
> too big for some curses implementations).
And given it provide
On Thu, May 18, 2006 at 04:27:15PM -0400, Aaron Davies wrote:
> Do you guys have any suggestions for suppressing flow control? I'm
> following a previous reccomendation and running screen on windows
> under PuTTY/Cygterm, but the flow control behavior of ^S is making
> emacs impossible to use. Is t
