# Re: [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas

1 messages from 2012-05-21 to 2012-05-21. Participants: Matt Seitz (matseitz).
Thread: https://gitlist.dev/t/30583

## Matt Seitz (matseitz), 2012-05-21 23:51

Subject: Re: [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas
Message-ID: <70952A932255A2489522275A628B97C31348C4AB@xmb-sjc-233.amer.cisco.com>
URL: https://gitlist.dev/e/70952A932255A2489522275A628B97C31348C4AB%40xmb-sjc-233.amer.cisco.com

```
"Junio C Hamano" <gitster@pobox.com> wrote in message
news:<7vaa116ulx.fsf@alter.siamese.dyndns.org>...
> 
> If you _only_ allow editors that understands windows style paths, your
> patch may make sense, but doesn't it break editors that wants only
POSIX
> style paths?

The Cygwin Users' Guide says "Using native Win32 paths in Cygwin, while
possible, is generally inadvisable."

http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32

Is this similar to the problem of line ending (POSIX lf vs. Windows
cr-lf)?  Windows Notepad won't correctly display files with lf line
endings, either.
So maybe this should be a configuration option, as with line endings?

```