Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Wed, 6 Sep 2000 11:07:45 -0400 To: cygwin@sources.redhat.com Subject: Re: i/o STOP + CONT (bash?) problem Message-ID: <20000906110745.A13563@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20000906121815.23143.qmail@web116.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20000906121815.23143.qmail@web116.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Sep 06, 2000 at 05:18:15AM -0700 On Wed, Sep 06, 2000 at 05:18:15AM -0700, Earnie Boyd wrote: >--- Benjamin Low wrote: >>What happens when you try ctrl-S/Q within bash? >> > >When using bash in rxvt C-s hangs the i/o if there is any i/o in >process. If I C-s before keyboard i/o it will hang upon the first >keystroke. If I'm output to the terminal and C-s it will hang. This >is regardless of the `tty' setting. > >When using bash in a DOS console window C-s and C-q work properly >regardless of the `tty' setting. Now the question is, who is at fault, >Cygwin or rxvt? I don't know. I've seen this bug report circulating for years. It's a shame that no one is motivated enough to actually debug the problem. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com