X-Recipient: archive-cygwin AT delorie DOT 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:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=rw+EBcjeyiqOYueS FPLl3J0PxP2dECi2c/wczYv9j8b4qUAk8frTFXWsCylkGzHmAsoXjnzm64nXTWhC OkJcNE1Hd8Y41QxzMtMFUexaQ27RoODg1qq3OM2BwbFJSDG9etTnPyFci9x8hala L8BNQAEtyrqHN0mBDhKnbhPv0Yo= 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:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=ww6XmPjfTM5usjSVCrebsH zQHQ8=; b=ESrVxeNJZl7xzxSBWSTGN43wgh69lhBD5ql6Yd+INpJlgcNB2PXu+c BEq/qABWGgBkWtXtquMgM2Jd0UznGJ2wuQoV3sae20WEEtSeDMSA16sHdjBxIwsf 8NBfO2La8bqpKYT69A2GmqRERjaHeW9iJ4eYgQ8B5kCxk9NWOz3WE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.9 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,NO_RDNS_DOTCOM_HELO,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*Ad:U*reply-to-list-only-lh, HReply-to:D*com, larry, HContent-type:flowed X-HELO: vms173009pub.verizon.net X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=VvtTO6+n c=1 sm=1 tr=0 a=FJ1kTJ0/xm5uTekQe8vMdQ==:117 a=IkcTkHD0fZMA:10 a=CH0kA5CcgfcA:10 a=_oNQklMPik-lrsEB-90A:9 a=QEXdDO2ut3YA:10 Reply-to: cygwin AT cygwin DOT com Subject: Re: Cygwin shell eats Windows exceptions? References: <384029be-4060-cb6b-d1e5-ea88cccb5999 AT Shaw DOT ca> <895baaa1-50d4-129f-1737-5621f7ed72b9 AT gmail DOT com> To: cygwin AT cygwin DOT com From: "Larry Hall (Cygwin)" Message-id: <57FFFA02.8020203@cygwin.com> Date: Thu, 13 Oct 2016 17:17:54 -0400 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit On 10/13/2016 03:00 PM, Bill Smith wrote: >> What if you 'cmd.exe /c foo.exe' from the Cygwin shell? Will the Dialogue >> popup box occur? If so you can provide a sh script foo to execute the >> foo.exe file. > [Bill Smith] > Thanks for the suggestion but that doesn't work. If I try to open a > command prompt from a Cygwin shell (just type in "cmd"), I get the same > behavior where I don't see the popup. If I run "cygstart cmd.exe", then > running the program from the command prompt will generate the popup. I believe the heart of your question is whether command-line utilities run under a Cygwin shell react to a terminal exception the same way as when run outside the shell. The answer, as you've found, is no, they don't. This is by design and there isn't a "switch" to flip to get around it. The point is that on Linux/Unix platforms, command-line utilities do not pop up windows, or any other kind of UI, which seek user input. Doing so can cause scripted processes to appear to "hang" and clutter the desktop. There was a time, long ago, where Cygwin command line utilities would do exactly that and the behavior was changed to return the error code and move on, just as would happen under Linux/Unix. Hope that helps, -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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