On Wed, Jun 29, 2011 at 12:27 PM, Adam Kellas wrote:
> On Wed, Jun 29, 2011 at 12:12 PM, Erik Osheim
> wrote:
>> Did you just try -RR without -x?
>
> I've been trying -RR alone recently and it seems close but not right.
> I'm not ready to characterize the problem yet, so will come back when
> I'
On Wednesday, June 29, 2011, Adam Kellas wrote:
> On Wed, Jun 29, 2011 at 12:12 PM, Erik Osheim
> wrote:
>> Did you just try -RR without -x?
>
> I've been trying -RR alone recently and it seems close but not right.
> I'm not ready to characterize the problem yet, so will come back when
> I've do
On 29.06.11,12:26, Adam Kellas wrote:
> Ramon,
>
> I think I failed to make the desired usage model clear. I gather most
> people are in the mode of (a) log in, then (b) run "screen", and (c)
> use screen thereafter to multiplex sessions. But my goal is to make
> use of screen completely invisible
On Wed, Jun 29, 2011 at 12:12 PM, Erik Osheim wrote:
> Did you just try -RR without -x?
I've been trying -RR alone recently and it seems close but not right.
I'm not ready to characterize the problem yet, so will come back when
I've done so.
Thanks,
AK
__
On Wed, Jun 29, 2011 at 7:49 AM, Erik Osheim wrote:
> On Tue, Jun 28, 2011 at 09:28:42AM -0400, Adam Kellas wrote:
>> Can anyone tell me the combination of flags to make this work?
>
> I'm not sure, but I think screen -x -RR may be what you want.
No, it's close but not exactly right. If there is
Ramon,
I think I failed to make the desired usage model clear. I gather most
people are in the mode of (a) log in, then (b) run "screen", and (c)
use screen thereafter to multiplex sessions. But my goal is to make
use of screen completely invisible[*]. In PuTTY one of the
configurables is the ssh
On Wed, Jun 29, 2011 at 12:07:54PM -0700, Adam Kellas wrote:
> No, it's close but not exactly right. If there is a free session this
> will attach to it (good). But if not, instead of creating a new one
> (which is what I want) it shares an existing one (bad).
>
> It's frustrating because there ar
On Tue, Jun 28, 2011 at 09:28:42AM -0400, Adam Kellas wrote:
> Can anyone tell me the combination of flags to make this work?
I'm not sure, but I think screen -x -RR may be what you want.
-- Erik
___
screen-users mailing list
screen-users@gnu.org
https
On 6/28/2011 9:28 AM, Adam Kellas wrote:
Bottom line, it's a very simpleminded use case; I want screen to do
nothing except preserve my sessions across disconnect. I.e. if I open
3 putty sessions I want 3 different shell prompts in 3 screen windows.
If I then reboot the laptop I want my first 3
I would first name your session something informative like "development" or
"testing" you can do that sending a commands to screen with C - a
: sessionname DEV
Then when you reconnect it would be screen -r DEV
You could also just add a line to your .screenrc file. There is also
another solution.
Now I've found -RR which is a lot closer to what I need. That may be
enough. Thanks and sorry for the noise.
AK
On Tue, Jun 28, 2011 at 9:28 AM, Adam Kellas wrote:
> I have a really simple use case for screen. I like to use PuTTY from
> my Windows laptop to Linux because PuTTY is a very nice ter
I have a really simple use case for screen. I like to use PuTTY from
my Windows laptop to Linux because PuTTY is a very nice terminal
emulator. The only problem I have with this is that when the network
connection drops, as in when I move around with the laptop, the PuTTY
session disconnects and al
12 matches
Mail list logo