MIME-Version: 1.0
In-Reply-To: <4BF1B307.20507@ntlworld.com>
References: <4BF1B307.20507@ntlworld.com>
Date: Tue, 18 May 2010 21:59:42 +0300
Message-ID: <AANLkTimMdAuJA9WeIwymMOmFDx4TXjuhgykBtIR1qXrO@mail.gmail.com>
Subject: Re: 1.7.5 cannot bg mintty
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 18/05/2010, cy.20.superconductor wrote:
> I sometimes forget to append a & when opening a new mintty from an
> existing mintty. With rxvt this was never a problem, just ^Z and bg in
> the parent terminal (my shell is bash  3.2.49-23). This doesn't seem to
> work for mintty (0.6.2-1) though - although it seems that the job has
> has been put into the background it never becomes possible to type
> anything into the newly spawned terminal window after ^Z has been used.
>
> If I spawn an rxvt from a mintty (or indeed an rxvt from an rxvt) using
> ^Z and bg works without any problems. I can't see anything obviously
> different in the output of stty -a between my rxvt and mintty.
>
> If I start a mintty with a &, fg it and then bg it again, the same
> effect occurs - it becomes impossible to type anything into the child
> mintty.
>
> I can an alias to avoid tripping myself up on this all the time, but it
> seemed worth querying. Is there something I'm missing or a setting
> needed somewhere to make mintty background-able (or indeed does anyone
> else experience this behaviour?)

Thanks for the report, I'll look into this when I get back from holiday.

Btw, you can also start a new mintty using Alt+F2.

Andy

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