public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex@alumni.utexas.net>
To: cygwin@cygwin.com
Subject: Re: screen
Date: Wed, 15 Jun 2005 14:11:00 -0000	[thread overview]
Message-ID: <8207v1hoka6k$.1wpcw4ne3a51q.dlg@40tude.net> (raw)
In-Reply-To: <42AF862C.3050900@ekit-inc.com>

>> Yes, the reattachment problem is now solved AFAICT, using Cygwin 1.5.17 or 
>> later.  Most of it works just fine, but there's one problem that I haven't 
>> solved yet:  when you detach a session, it stays bound to its parent 
>> shell.  So if you then try to exit the parent shell, it hangs.  You can 
>> terminate the parent shell, but then screen exits too.  Obviously this 
>> takes away one of the big advantages of screen, which is the ability to 
>> detach a session, leaving it running in the background, and then reattach 
>> later from a different terminal.
> 
> hmm I have not had that problem? I run rxvt's with bash and can exit all
> terminals leaving no bash process but screen lives on. I can then fire
> up another shell and re-connect to screen and any jobs it has running.
> (ie it works just like it should!)

Interesting.  Okay, I hadn't noticed this before, but the problem does
seem to be particular to the Cygwin console.  It doesn't occur with
rxvt.  Also, it doesn't occur in the Cygwin console if I start a
subshell first, and invoke screen from there.  Maybe useful to know.
Still, I do want to solve the problem before I release screen.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2005-06-15 13:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15  7:44 screen Shaun Broadbent
2005-06-15 14:11 ` Andrew Schulman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15 21:27 screen [ping cgf] Andrew Schulman
2007-02-15 21:47 ` Christopher Faylor
2007-02-16  1:18   ` Andrew Schulman
2007-02-16 14:09     ` Christopher Faylor
2007-02-16 18:01       ` screen Andrew Schulman
2007-02-16 21:14         ` screen Christopher Faylor
2007-02-18 16:29           ` screen Christopher Layne
2007-02-18 16:49             ` screen Christopher Faylor
     [not found] <42AE548B.6050905@ekit-inc.com>
2005-06-14 12:14 ` screen Schulman.Andrew
2003-04-26 16:24 screen Cant
2003-04-29 19:18 ` screen Karsten M. Self
2003-04-29 21:07   ` screen Igor Pechtchanski
2003-04-30  2:50     ` screen Karsten M. Self
2003-04-12  0:43 screen Cant
2003-04-12  0:50 ` screen Igor Pechtchanski
2003-04-12  0:51   ` screen Cant
2003-04-12  0:53     ` screen Igor Pechtchanski
2003-04-12  0:56       ` screen Cant
2003-04-12  0:56         ` screen Cant
1998-10-04 15:45 Screen cv23iuy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='8207v1hoka6k$.1wpcw4ne3a51q.dlg@40tude.net' \
    --to=andrex@alumni.utexas.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).