DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=ozJ
	fRoEgMwSOqLpSopSQ9SydqV20kWUqyNOBsPM5yhMCIP721HvwIOdiixiVnruTZR6
	W/IjAU1vztYVLXCdRhXEFcXr/FvgK8Zgy6hgX2/y0Hb0Fvjaw9SVQyINcUDBVeNs
	IEpzI/avLK2AkRVMIq2VQB7uoEKMdyINfWAIo7to=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Brian Clifton <brian AT clifton DOT me>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: introduction, fix for npm w.r.t. git, and questions
Date: Wed, 20 Apr 2016 15:21:27 +0000
Message-ID: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0@BLUPR03MB230.namprd03.prod.outlook.com>
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2016 15:21:27.9776 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8bdfec6b-c71e-4ab9-8b6b-9de7cf58a5f5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB231
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u3KFLrWD025659

Hi folks,

(I've never joined a mailing list so please bear with me as I learn how this works)

########
Quick intro
########
My name is Brian, I'm a developer at a hosting company in Arizona, USA and I really enjoy Cygwin. I mostly use it at home and I appreciate all of the work everyone has done. It has made my life easier for sure.

########
Git using Windows paths
########
I saw the email chain regarding Git using Windows paths; I wanted to share that I've been fighting that too. Specifically, npm will fail npm installs because it will try to use the Windows path. I submitted the following PR to fix that:
https://github.com/npm/npm/pull/12366

The PR was denied but you can see the patch made and manually apply this yourself.  Since it was rejected, I'm trying to find a better way to do this. I am considering a solution by creating a git() function in my bashrc like so:
function git {
    for var in "$@"
    do
        if [[ $var == *":\\"* ]]; then
            $var="$(cygpath $var)" #this doesn't work, but the idea is to do something like this
        fi
    done
    command git "$@"
}

I wanted to ask what you all think about this approach. Since Cygwin converts the paths, filtering any git input through cygpath makes sense, IMO. With how many folks experience issues w/ git on Cygwin, I'd like to help popularize *some* kind of fix, whatever it might be, since NPM and likely other projects are not willing to support Cygwin.

########
Quick question(s)
########
Is the website source available in git? If so, would folks be open to PRs with styling changes and/or documentation updates?

Thanks
Brian

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