X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=DAn+l84U1bvjuoGa2cO8m+grwi4mW9xix3AWR8bnY1b
	vwWl+fGbIuiFwH9qIaonlQPkweO+UISPAcU+7mkHpEasnek4J313PFmg0VuF6Avt
	XY/yGskJs6KTs0HIytRdGi9uAYA8ltaSnhCd0s3iE4Y6RUdkDYiWORgU0L7Jcpbo
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=4KUIb1XZwi87nwBdDk2eXA2dK3E=; b=ie1f6c0A1nqo3pWdF
	BWxekdEPhoaA84eRikAeUCcz0gAM97eCCu7zC+fGOrE9QBIyO8rmttEWQB4u5T4n
	Q8ieAHkmSffH/PUESeFhnSwvgQTXuCCQ7CnW+uuMHFidj9uDHF/FN9S8OAFn0Vfb
	uX4A9suITZZMFxwT0QLOi3edgw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-qg0-f51.google.com
X-Received: by 10.224.26.71 with SMTP id d7mr27918905qac.29.1396805453862;        Sun, 06 Apr 2014 10:30:53 -0700 (PDT)
Message-ID: <53418F52.2080206@gmail.com>
Date: Sun, 06 Apr 2014 13:30:58 -0400
From: Max Polk <maxpolk@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 1.7.28: Ctrl-C not working reliably
References: <BLU404-EAS2010888D40BD8823CCAC899D96F0@phx.gbl> <53406AEF.80309@cygwin.com>
In-Reply-To: <53406AEF.80309@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 4/5/2014 4:43 PM, Larry Hall (Cygwin) wrote:
> On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
>> 2) Type: ssh blargh  # or any non-existent host
>> 3) Press Ctrl-C immediately after that
>>
>> On my machine, the Ctrl-C doesn't stop SSH from trying to look up the
>> non-existent host, it keeps going until it gives up and times out (which
>
> Right, I noticed no difference in behavior between either.  But ^C worked
> for me, although with a slight (1 second) delay.  Interestingly enough,
> using a qualified name (i.e. blargh.com) made it respond immediately.
>

I speculate that the 1-second delay is the time it takes for *console 
output* to occur.  The control-c is not noticed or acted upon until 
console output occurs.  Since you hit control-c before output occurs, it 
has to wait.  Then the moment the first character begins to print, it is 
interrupted from printing and you see not output.  But secretly it was 
stdout all along that was necessary. Again, I have seen this enough over 
the years for me to suggest this, but have no real knowledge why and 
can't prove it.

--
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

