public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Accessing long filesystem paths using Python
Date: Mon, 7 Nov 2022 10:33:25 +0100	[thread overview]
Message-ID: <Y2jQ5aAlgKuNreVG@calimero.vinschen.de> (raw)
In-Reply-To: <AM6PR08MB44210F777A836F5E5A5FF507E63B9@AM6PR08MB4421.eurprd08.prod.outlook.com>

Hi Fridjof,

Please don't top-post.

On Nov  4 13:30, Fritjof Bornebusch wrote:
> On Nov  4 13:57, marco atzeri wrote:
>> On Fri, Nov 4, 2022 at 1:16 PM Fritjof Bornebusch 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..
> 
> Jep,
> 
> No success.

Works for me:

======================================================================
$ cat > longp.sh <<EOF
#!/bin/bash

POSIX_MAX=4096
# 240 chars per path component
DIRNAM="123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"

LPATH=/tmp
cd /tmp

while [ $(echo -n "$LPATH" | wc -c) -lt $POSIX_MAX ]
do
  mkdir "$DIRNAM" || exit 1
  LPATH="$LPATH/$DIRNAM"
  ls -d "$LPATH" || exit 2
  cd "$LPATH" || exit 3
  echo "Current length: $(echo -n $LPATH | wc -c)"
  sleep 1
done
EOF
$ chmod +x longp.sh
$ ./longp.sh
/tmp/123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
Current length: 245
[...]
12345678901234567890/123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
Current length: 4101
$
======================================================================

If you have specific trouble, please provide a specific, simple testcase,
preferredly in plain C or as shell script.


Thanks,
Corinna

      reply	other threads:[~2022-11-07  9:33 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
2022-11-07  9:33       ` Corinna Vinschen [this message]

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=Y2jQ5aAlgKuNreVG@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).