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=tQ3ecbTMV1qtwuMm
	HFhwgUPJryqGjryGlLke+/fUF6KV7LuRpSlKYM1lQEU4oheVmUgu6yObexUKqr/j
	mVplUwlp9MfcgMTLaUsaId5/TFc/MCttkSOULS99KO8YL9pg++5azug0ZJR1D6zt
	kVcAofGKZgvAA+TTCPMO9LOhjJ8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: moss@cs.umass.edu
Subject: Re: introduction, fix for npm w.r.t. git, and questions
References: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0@BLUPR03MB230.namprd03.prod.outlook.com>
To: cygwin@cygwin.com
From: Eliot Moss <moss@cs.umass.edu>
Message-ID: <5717A0BD.9090201@cs.umass.edu>
Date: Wed, 20 Apr 2016 11:31:09 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0@BLUPR03MB230.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

I see no reason why a function similar on concept to what you write,
i.e., one that applies cygpath to convert full Windows paths to cygwin
style paths, should not work.  I have a number of simple function that
do the opposite, allowing me to invoke Windows programs (such as Word)
with cygwin paths by converting to the equivalent Windows path first.

This requires careful attention to quoting and such, but is conceptually
not that hard.  If you end up struggling with it, I can probably write
something suitable for you ...

Eliot Moss

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