This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: ^Z under current Cygwin problem
- To: "Andrej Borsenkow" <Andrej dot Borsenkow at mow dot siemens dot ru>,<cygwin at cygwin dot com>
- Subject: RE: ^Z under current Cygwin problem
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- Date: Tue, 20 Feb 2001 10:20:02 -0500
- References: <20010219143445.A19549@redhat.com>
At 12:54 AM 2/20/2001, 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.
>
>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?
If we could say that Cygwin is bug-compatible with Linux, I think that would
be saying allot (in a good way). Of course, if there's a way to fix those
bugs in Cygwin, I think that's a laudable goal too. I encourage anyone who
is interested to investigate and fix this and any other bug they find. Let
it not be said that Cygwin is complacent with bugs!;-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple