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:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:content-type; q=dns; s= default; b=bxUyCLwepCWTEW9aCJwgcrBeUDngYXgy+/LmnLw4JD7U2yyn1G9iM BA4CSTr1k2NP/QZ9Ll3e2NEI4dlh0OaGJpF6irKrxrMTFJ++AHWfQDSWsOCQF+Ak Y6tzKKT5Hl+4ocNPMJic7B91M6pGq72pdR73fL4NNe3bmntr8vWqAM= 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:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:content-type; s=default; bh=6TLD58m2zlCmRAl599tqsmoBfeM=; b=gzmEsGdybYvqysQQp0tcErlHYNAv Xdh2I3v7HijT0UhtXC606QS7eqeeDh1Pd2aUgfCkwNugyd+I7E5yfGTOK3inAdT5 7JgkpZm7PgspHv64UEDmcajAaCr3IL2e4MS+Yk/eEpX/nbsbJlxXsaPqAMSQ1mbw 2zVev0XAcxm/144= 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=-0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,FREEMAIL_REPLYTO_END_DIGIT,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: nm40-vm10.bullet.mail.gq1.yahoo.com References: <1414155946 DOT 62587 DOT YahooMailNeo AT web162803 DOT mail DOT bf1 DOT yahoo DOT com> <20141024135339 DOT GM20607 AT calimero DOT vinschen DOT de> <1414163944 DOT 58941 DOT YahooMailNeo AT web162803 DOT mail DOT bf1 DOT yahoo DOT com> <544A6FB4 DOT 5070004 AT redhat DOT com> Message-ID: <1414168852.48564.YahooMailNeo@web162802.mail.bf1.yahoo.com> Date: Fri, 24 Oct 2014 09:40:52 -0700 From: John Wiersba Reply-To: John Wiersba Subject: Re: Why can't run.exe execute a shebang script directly? To: Eric Blake , "cygwin AT cygwin DOT com" In-Reply-To: <544A6FB4.5070004@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes > From: Eric Blake > On 10/24/2014 09:19 AM, John Wiersba wrote: > >> I thought that all (or virtually all) cygwin-supplied programs that start >> other programs use the cygwin1.dll execve(2) emulation to start them, > because >> the execve emulation can be used to start *both* cygwin programs and > windows >> native programs. Or at least it seems that way to me. >> >> Is there be in drawback to having run.exe start its target program using >> the execve emulation in cygwin1.dll, rather than using a Windows call to >> start the target executable? > > run.exe is special. In order to hide consoles, it MUST use native > windows API instead of cygwin1.dll calls. OK -- I guess that settles it, then! Thanks! -- 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