public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sources.redhat.com
Subject: Re: i/o STOP + CONT (bash?) problem
Date: Wed, 06 Sep 2000 08:08:00 -0000	[thread overview]
Message-ID: <20000906110745.A13563@cygnus.com> (raw)
In-Reply-To: <20000906121815.23143.qmail@web116.yahoomail.com>

On Wed, Sep 06, 2000 at 05:18:15AM -0700, Earnie Boyd wrote:
>--- Benjamin Low <bdlow@nortelnetworks.com> 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

  reply	other threads:[~2000-09-06  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-06  5:18 Earnie Boyd
2000-09-06  8:08 ` Chris Faylor [this message]
2000-09-06 16:45 ` Benjamin Low
2000-09-06 17:24   ` Chris Faylor
2000-09-06 18:19     ` Chris Faylor
  -- strict thread matches above, loose matches on Subject: below --
2000-09-06 12:31 Earnie Boyd
2000-09-06  9:38 Rick Rankin
2000-09-06 10:03 ` Chris Faylor
     [not found] <968167382.14182.ezmlm@sources.redhat.com>
2000-09-05 18:58 ` Benjamin Low
2000-09-05 19:08   ` Chris Faylor
2000-09-05 21:53     ` Benjamin Low
2000-09-05 22:35       ` Chris Faylor
2000-09-05 22:37         ` Chris Faylor

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=20000906110745.A13563@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@sources.redhat.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).