This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: ^Z under current Cygwin problem
- To: cygwin at cygwin dot com
- Subject: Re: ^Z under current Cygwin problem
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Mon, 5 Mar 2001 11:38:42 -0500
- References: <20010219143445.A19549@redhat.com> <000001c09b01$a0cce8f0$21c9ca95@mow.siemens.ru> <20010220110917.D29217@redhat.com>
- Reply-To: cygwin at cygwin dot com
On Tue, Feb 20, 2001 at 11:09:17AM -0500, Christopher Faylor wrote:
>On Tue, Feb 20, 2001 at 08:54:46AM +0300, Andrej Borsenkow wrote:
>>> On Mon, Feb 19, 2001 at 01:12:43PM +0300, Andrej Borsenkow wrote:
>>> >I thought it was zsh problem but it happens with vanilla bash as well:
>>> >
>>> >- the "sleep 100000" is can be suspended but exits immediately after fg'ing
>>>
>>> Same thing on linux.
>>>
>>
>>Should Cygwin carry over Linux bugs?:
>>
>>bor@itsrm2% sleep 100000
>>^Z
>>zsh: suspended sleep 100000
>>bor@itsrm2% fg
>>[1] + continued sleep 100000
>>
>>it's not going to exit.
>
>It's not a bug.
>
>>O.K., let's consider it a bug in GNU sleep implementation. What about another
>>case (cat, tr etc)? This does not look right, do it?
>
>No. It isn't right. I know what is causing it. I'm mulling over a fix now.
>It was caused by an optimization that I am loathe to turn off but that may
>be the ultimate solution.
This should be fixed in snapshots newer than 4-Mar-2001.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple