On Fri, Oct 9, 2009 at 19:34, Ryan Lynch wrote:
> (CCing the Screen users list, in case anybody else is interested in this,
> too.)
>
> On Tue, Oct 6, 2009 at 18:19, Ryan Lynch wrote:
>> When I've cleaned it up enough for human consumption, I'll post a copy
>
(CCing the Screen users list, in case anybody else is interested in this, too.)
On Tue, Oct 6, 2009 at 18:19, Ryan Lynch wrote:
> When I've cleaned it up enough for human consumption, I'll post a copy
> of the whole script.
I've attached a copy of the script I'm cu
On Thu, Oct 1, 2009 at 18:32, Ryan Lynch wrote:
> On Thu, Oct 1, 2009 at 15:58, Sadrul Habib Chowdhury wrote:
>> properly produce the response to send back as the query result. I am
>> going to update the 'info', 'lastmsg' and 'windows' commands
On Thu, Oct 1, 2009 at 15:58, Sadrul Habib Chowdhury wrote:
> properly produce the response to send back as the query result. I am
> going to update the 'info', 'lastmsg' and 'windows' commands for this
> first. What other commands do you think a script might want to query?
Great to hear that, I'
I know that I can send commands to a running 'screen' session, using
the `screen -X ...` option, but it seems like this is a
one-way street. This command never seems to return any output--if
there is any response, it's usually only visible inside the screen
session, itself.
Is if possible to quer
I've set up my .bashrc to automatically attach me to a Screen session
when I open a new BASH shell (unless the env var $STY is set, or $TERM
contains 'screen', or the shell isn't interactive). I have some
wrapper logic, but the basic algorithm is:
* Always use '__DEFAULT' as a Screen session nam
