Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 29 May 2003 05:11:50 -0700 From: Dario Alcocer To: cygwin AT cygwin DOT com Subject: Re: problem suspending "man bash" (intermittent) Message-ID: <20030529051150.B4311@ns.helixdigital.com> References: <20030529050426 DOT A4311 AT ns DOT helixdigital DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030529050426.A4311@ns.helixdigital.com>; from alcocer@helixdigital.com on Thu, May 29, 2003 at 05:04:26AM -0700 On Thu, May 29, 2003 at 05:04:26AM -0700, Dario Alcocer wrote: > I tried reproducing this, but I don't get the same exact results. For > me, it takes 7 or 8 tries, and all I get is a missing '[1]+ Stopped' > message from bash; the next keystrokes still go to bash, though. The > problem seems to go away if I use 'fg' instead of 'fg man'. I was not > able to s/I was not\nable to// -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. alcocer AT helixdigital DOT com -- http://www.helixdigital.com -- 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/