From: Fritjof Bornebusch <fritjof.bornebusch@prover.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Accessing long filesystem paths using Python
Date: Fri, 4 Nov 2022 12:15:45 +0000 [thread overview]
Message-ID: <AM6PR08MB4421530580BFE77F7508D890E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <AM6PR08MB4421EE65314E815E8BA73753E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Hi,
I need to write files whose path exceed the maximum value of 260 characters.
Using Windows paths, you can add \\?\ as prefix, e.g., \\?\C:\Users\foo\bar\<file://%3f/C:/Users/foo/bar/>....
However, it seems like this is not the case in Cygwin. When I use \\?\/home/foo/bar<file://%3f/home/foo/bar>, I get no file pointer back.
Does someone have a clue how I can bypass this?
Best,
Fritjof
next parent reply other threads:[~2022-11-04 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM6PR08MB4421EE65314E815E8BA73753E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com>
2022-11-04 12:15 ` Fritjof Bornebusch [this message]
2022-11-04 12:56 ` marco atzeri
2022-11-04 13:30 ` Fritjof Bornebusch
2022-11-07 9:33 ` Corinna Vinschen
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=AM6PR08MB4421530580BFE77F7508D890E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com \
--to=fritjof.bornebusch@prover.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).