introduction, fix for npm w.r.t. git, and questions

[Brian Clifton <brian@clifton.me>]

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