RE: Cygwin Git with Windows paths
- From
Randall S. Becker <rsbecker@nexbridge.com>
- Date
- Nov 19, 2018, 02:11 UTC
- Message-ID
- <005801d47fad$345d5a70$9d180f50$@nexbridge.com>
- In-Reply-To
- <xmqqsgzydj6n.fsf@gitster-ct.c.googlers.com>
Show 15 quoted lines
> -----Original Message----- > From: git-owner@vger.kernel.org <git-owner@vger.kernel.org> On Behalf Of > Junio C Hamano > Sent: November 18, 2018 19:07 > To: Torsten Bögershausen <tboegi@web.de> > Cc: Steven Penny <svnpenn@gmail.com>; git@vger.kernel.org > Subject: Re: Cygwin Git with Windows paths > > Torsten Bögershausen <tboegi@web.de> writes: > > > And it may even be that we need a special handling for the "\" to be > > treated as "/". > > I do not do Windows, but is_dir_sep() needs to be tweaked if you want to do > that.
Heavy Cygwin user here. It is used in my environment for cross-compilation. Everything should be done using / separators in Cygwin, not \. So /cygdrive/c, /cygdrive/d always prefaces the path rather than C:\ or D:\, which won't parse. It is, essentially, a bash environment, including that git completions work properly. Backslash ends up doing what it would in bash.