DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=l1Y7o/3uBym2iQ07
	quhtbAOwHeYS0Lx9E9IyEwoZWBUnJZn7eFvtoOJGNq3js1GPGiEmQk2Htq8wazpB
	OjOcu302s8AjDXe8XaMDJflKpZO55pabCeZryW4Hi6OoudDT5qdJfYIVw94Hy44q
	lS0cKcHjLlhQZqQSX8XtF7znCpI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 6 Aug 2015 14:30:35 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <501181462.20150806143035@yandex.ru>
To: Nicholas Clark <nicholas.clark@gmail.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
In-Reply-To: <CAKNeuBqASXv_LC0vJC3F9bVDauQJ-1tWTT5L+to4JbGejyaXrw@mail.gmail.com>
References: <announce.20150803131950.GA18878@calimero.vinschen.de>   <55BFB64C.1010802@towo.net> <20150803192940.GA19315@calimero.vinschen.de>  <loom.20150804T094839-714@post.gmane.org>  <895515CC-6BB7-41E7-AEA5-30FBBE071153@etr-usa.com>  <87wpxac2bj.fsf@Rainer.invalid> <20150805075435.GP17917@calimero.vinschen.de>  <1324339149.20150805194114@yandex.ru>  <CAKNeuBqe_w79RBcC=iRki7kZeDQdBen85kWuPZESO0SCGaCUAQ@mail.gmail.com>  <897487143.20150806031430@yandex.ru>  <CAKNeuBqASXv_LC0vJC3F9bVDauQJ-1tWTT5L+to4JbGejyaXrw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Nicholas Clark!

> You're certainly right that there are nicer ways to write that script.
> My point with the sample script above is that I'm currently using a
> Windows-style HOME path, and it works fine.

If it would stop working, you'll have to o and revisit your mess to pull the
cruft out of the pipes.

> Chances are there are a bunch of other users out there who also use a
> Windows-style HOME path in messy .bat files - I just wanted to
> illuminate that making Windows paths illegal is likely to break a
> whole bunch of users' scripts, and really offers no benefit.

Chances are, they can go and revisit their mess once in a lifetime.
When 1.7.35 came out, I went and dug up every corner of my system to make sure
I no longer have the need for wrappers like yours.

Recently I started to write portable scripts for my private project and I've
replaced Cygwin's /bin/sh (which is in fact bash) with a symlink to /bin/dash.
We'll see how far I can go with it. Already found a number of scripts that
break under strict POSIX shell. None of them Cygwin scripts. Yet.


-- 
With best regards,
Andrey Repin
Thursday, August 6, 2015 14:26:24

Sorry for my terrible english...


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