public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fritjof Bornebusch <fritjof.bornebusch@prover.com>
To: marco atzeri <marco.atzeri@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Accessing long filesystem paths using Python
Date: Fri, 4 Nov 2022 13:30:57 +0000	[thread overview]
Message-ID: <AM6PR08MB44210F777A836F5E5A5FF507E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAB8Xom_kn8VZm29ot251=85fp5m-O8y0kn3jL3rHObmXbKGZRA@mail.gmail.com>

Jep,

No success.

-----Original Message-----
From: marco atzeri <marco.atzeri@gmail.com> 
Sent: Friday, 4 November 2022 13:57
To: Fritjof Bornebusch <fritjof.bornebusch@prover.com>
Cc: cygwin@cygwin.com
Subject: Re: Accessing long filesystem paths using Python

On Fri, Nov 4, 2022 at 1:16 PM Fritjof Bornebusch <fritjof.bornebusch@prover.com> wrote:
>
> 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
>

Have you tried POSIX style ?
/cygdrive/C/Users/foo/bar..

  reply	other threads:[~2022-11-04 13:31 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
2022-11-04 12:56   ` marco atzeri
2022-11-04 13:30     ` Fritjof Bornebusch [this message]
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=AM6PR08MB44210F777A836F5E5A5FF507E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com \
    --to=fritjof.bornebusch@prover.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).