X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.9 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_NONE,TW_RX X-Spam-Check-By: sourceware.org Message-ID: <4BF1B307.20507@ntlworld.com> Date: Mon, 17 May 2010 22:20:07 +0100 From: cy DOT 20 DOT superconductor AT xoxy DOT net User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: 1.7.5 cannot bg mintty Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spamgourmet: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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, Paul -- 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