From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: Strange behavior when executing programs
Date: Mon, 12 Dec 2022 16:42:54 +0100 [thread overview]
Message-ID: <Y5dL/vnXcTu0gcqE@calimero.vinschen.de> (raw)
In-Reply-To: <DM8PR09MB70958AA059C4DB484DEA27B3A5E29@DM8PR09MB7095.namprd09.prod.outlook.com>
On Dec 12 15:29, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > The problem is that resolved paths may become longer than MAX_PATH.
>
> Oh... But that'd be the same on any other OS that exceeds MAX_PATH, symlinking is going to help work around that,
> if the full path resolution was requested.
>
> BTW, about MAX_PATH -- was it Cygwin's or Windows'? If the former, can't it be enlarged?
Cygwin handles up to 32K paths for a long time, just like the Windows
kernel.
It's the native tools and the Win32 ANSI file-API still using MAX_PATH
as a path length restriction.
Corinna
next prev parent reply other threads:[~2022-12-12 15:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:21 Frank Redeker
2022-12-12 12:12 ` Corinna Vinschen
2022-12-12 12:46 ` Frank Redeker
2022-12-12 13:09 ` Corinna Vinschen
2022-12-13 9:51 ` Corinna Vinschen
2022-12-13 12:54 ` Frank Redeker
2022-12-13 14:15 ` Corinna Vinschen
2022-12-13 16:35 ` Frank Redeker
2022-12-13 16:54 ` Jon Turney
2022-12-13 17:04 ` Oskar Skog
2022-12-14 5:38 ` Frank Redeker
2022-12-14 10:14 ` Corinna Vinschen
2022-12-12 14:52 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-12 15:20 ` Corinna Vinschen
2022-12-12 15:29 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-12 15:40 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-12 15:42 ` Corinna Vinschen [this message]
2022-12-12 15:50 ` Corinna Vinschen
2022-12-12 15:22 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-12 15:41 ` Corinna Vinschen
2022-12-12 16:40 ` Frank Redeker
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=Y5dL/vnXcTu0gcqE@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).