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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=K3 5RaJKwB2+c4hGwbu7K8H5VYfOZouSsknv9WBs68n6f3q8qJwuZWm6pKEwKFK3/sz YUB95tafThAIw3j1j1UNm0I3QC08L1bOyoElsgNznGQ0fqGfz47iglSbETgvkn4v by52siNgJCu0P6ZItdGP3NgMAm0xtL+8AOVKp4uew= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=pn5Y8HQT nAZR/CtBK9thpnTCShE=; b=YyOzkb2/7nfFhXA/HUP+kv9ERjHg0TFASRT4imjX XYPDRtctHWGR/e9USDltNArIOU/svnrQUMWVZTvR6fntVYg0RVm2BZvHJlAj+KyU RQD3vBhdY2iUbsfm3qqlDWj5BR2D+HvoPZBgOC0L4MvBtpELBoO4P++XDHvOvjfX aH4= 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 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.224.78.11 with SMTP id i11mr646092qak.29.1369058818818; Mon, 20 May 2013 07:06:58 -0700 (PDT) In-Reply-To: <002401ce5562$47768a30$d6639e90$%fedin@samsung.com> References: <519A2341 DOT 5030708 AT openafs DOT org> <002401ce5562$47768a30$d6639e90$%fedin AT samsung DOT com> Date: Mon, 20 May 2013 10:06:58 -0400 Message-ID: Subject: Re: Patch for shutdown From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 On Mon, May 20, 2013 at 9:59 AM, Fedin Pavel wrote: > > At the other hand, IMHO, Windows .bat scripts are never run from wihin bash, and vice versa, UNIX .sh scripts are never run from within cmd.exe... I do this. Create a null (native, i.e. non-cygwin) program named #! and put it in PATH. Then my scripts can do ~~~~~ #!/cmd /c :: Dos batch commands ~~~~~ > And following the same logic we would need to teach our find.exe (already mentioned on this list) to understand Windows options instead of UNIX options... I think that would be a no go from the get go. > Even further, in terminal case, why have Cygwin at all ? It is different from Windows command line and this is confusing... > Oh, now I read the sarcasm. :/ -- 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