git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
MMMatt Seitz (matseitz) <matseitz@cisco.com>
Date
May 21, 2012, 23:51 UTC
Message-ID
<70952A932255A2489522275A628B97C31348C4AB@xmb-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?

Message 1 of 1 in “Re: [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas”
  1. Matt Seitz (matseitz)May 21, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.