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 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: Subject: RE: ^Z under current Cygwin problem Date: Tue, 20 Feb 2001 08:54:46 +0300 Message-ID: <000001c09b01$a0cce8f0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20010219143445.A19549@redhat.com> Importance: Normal > 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? -andrej -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple