delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2012/08/03/10:01:55

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <501BD762.80300@gmail.com>
References: <501AD5B9 DOT 5030005 AT gmail DOT com> <20120802230013 DOT GB6793 AT ednor DOT casa DOT cgf DOT cx> <CA+sc5mkhf+Ri1QOoFSTpn0xs0HeibpCo548rp67Th92Y4Sq-LQ AT mail DOT gmail DOT com> <501BD762 DOT 80300 AT gmail DOT com>
Date: Fri, 3 Aug 2012 10:01:22 -0400
Message-ID: <CA+sc5mkSXxqn7V_eXprPxs8pXQ4gW9vyYS+9Hw_98NQ-xFPxPA@mail.gmail.com>
Subject: Re: Ctrl+C not working with windows programs in Cygwin 1.7.16
From: Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, Aug 3, 2012 at 9:51 AM, marco atzeri wrote:
> On 8/3/2012 3:43 PM, Earnie Boyd wrote:
>>
>> On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
>>>
>>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>>>>
>>>> Steps to reproduce:
>>>>
>>>> 1. Start cygwin using cygwin.bat
>>>> 2. Run `ping -t google.com`
>>>> 3. Try breaking it with Ctrl+C
>>>>
>>>> Expected behaviur:
>>>> The ping breaks execution and the command prompt is shown and available
>>>>
>>>> Actual behaviour:
>>>> Nothing happens, ping loops until killed with `/usr/bin/kill -f PID`
>>>
>>>
>>> I don't have a "cygwin.bat" but if I start bash via Start->Run this
>>> works for me.  ping is interrupted by CTRL-C.
>>>
>>
>> If executed from mintty CTRL-C works to interrupt the process.  If
>> executed from a Windows console terminal (and I don't mean cmd.exe)
>
>
> a "windows console terminal" is cmd.exe, IMHO.
> There are no other console in windows as standard installation.
>

A console terminal is used for any process needing
stdin/stdout/stderr, that isn't just cmd.exe.

>> ping doesn't interrupt with CTRL-C.  Another interesting thing, ``run
>> bash --login -i'' starts the process but the Window closes with the
>> process in the background and I have to use the Task Manager to kill
>> it, Cygwin's kill doesn't kill it.  However ``run mintty'' works
>> regardless.
>
>
> have you checked the manual ?
>
> RUN(1)                            run 1.1.13 RUN(1)
>
> NAME
>        run - start programs with hidden console window

Ok, sorry, I assumed it was similar to cmd /c start.  But I should be
able to kill it with Cygwin's kill command.  Also the doing ``run bash
--login -i'' the terminal command prompt doesn't return to the issuing
job either.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019