From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Ctrl+C not working with windows programs in Cygwin 1.7.16
Date: Fri, 03 Aug 2012 14:06:00 -0000 [thread overview]
Message-ID: <CA+sc5mkSXxqn7V_eXprPxs8pXQ4gW9vyYS+9Hw_98NQ-xFPxPA@mail.gmail.com> (raw)
In-Reply-To: <501BD762.80300@gmail.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
next prev parent reply other threads:[~2012-08-03 14:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:34 Marcin Kielar
2012-08-02 21:02 ` Daniel Colascione
2012-08-02 21:22 ` Roger K. Wells
2012-08-02 21:35 ` Daniel Colascione
2012-08-02 21:55 ` Roger K. Wells
2012-08-03 12:48 ` Nellis, Kenneth
2012-08-03 13:34 ` Roger K. Wells
2012-08-03 13:57 ` Christopher Faylor
2012-08-03 14:01 ` K Stahl
2012-08-02 23:03 ` Christopher Faylor
2012-08-02 23:10 ` Daniel Colascione
2012-08-03 3:05 ` Christopher Faylor
2012-08-03 12:58 ` Roger K. Wells
2012-08-03 13:51 ` Earnie Boyd
2012-08-03 13:53 ` marco atzeri
2012-08-03 14:00 ` Christopher Faylor
2012-08-03 14:08 ` Christopher Faylor
2012-08-03 14:33 ` Corinna Vinschen
2012-08-03 15:57 ` Christopher Faylor
2012-08-03 14:06 ` Earnie Boyd [this message]
2012-08-07 8:45 ` Andrey Repin
2012-08-07 10:35 ` marco atzeri
2012-08-07 11:00 ` Corinna Vinschen
2012-08-07 14:55 ` Andrey Repin
2012-08-07 15:56 ` Corinna Vinschen
2012-08-03 17:32 ` Christopher Faylor
2012-08-03 18:51 ` Roger K. Wells
2012-08-03 19:19 ` Marcin Kielar
2012-08-03 22:34 ` Earnie Boyd
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=CA+sc5mkSXxqn7V_eXprPxs8pXQ4gW9vyYS+9Hw_98NQ-xFPxPA@mail.gmail.com \
--to=earnie@users.sourceforge.net \
--cc=cygwin@cygwin.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).