From: matthew patton <pattonme@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: misterious GIT failure (SOLVED)
Date: Sun, 17 Jan 2021 21:07:08 +0000 (UTC) [thread overview]
Message-ID: <1218339117.1507408.1610917628826@mail.yahoo.com> (raw)
In-Reply-To: <2213ecae-52ec-4148-9370-78b846fb26cc@SystematicSw.ab.ca>
On Sunday, January 17, 2021, 02:41:35 PM EST, Brian Inglis <brian.inglis@systematicsw.ab.ca> wrote:
> Sorry, it's been a few years now - there were a few issues testing various paths > using various directories and links that neither readlink nor realpath resolved
> absolutely and correctly, so I added the cygpath to and fro to give a consistent
> path to support ordering and duplicate checking.
I haven't run into a scenario yet where 'readlink' doesn't work. But I also don't intermix Windows with my Cygwin except in rare occasion. What IS absolutely NUTS is Cygwin's treatment of spaces in PATH elements - it magically escapes them but refuses to recognize escaped spaces; considers them invalid. All other environment variables spaces have to be treated properly.
Cygpath also blows up spectacularly when you feed '-w/-m' anything that isn't a syntactically perfect unix-style (colon delimited) character string.
next prev parent reply other threads:[~2021-01-17 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1742171701.1391964.1610730544471.ref@mail.yahoo.com>
2021-01-15 17:09 ` matthew patton
2021-01-15 17:29 ` Brian Inglis
2021-01-17 18:11 ` Andrey Repin
2021-01-17 19:41 ` Brian Inglis
2021-01-17 21:07 ` matthew patton [this message]
2021-01-17 22:24 ` David Dyck
2021-01-15 17:48 ` Ken Brown
2021-01-16 17:22 ` matthew patton
2021-01-16 17:35 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1218339117.1507408.1610917628826@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).