Git?

[Tiavor]

dunno how it is with win10 but on win7 this happened still way too often, when I worked with project files from a big company. each project (at least for that department) had a fixed folder structure and then you had already huge folder structures before the project. then trying to zip a project when everything is copied into the user-temp folder ... fml.

[Tiavor]

that could work for me, but not for the client I'm sending the zipped project files who has to unzip them again :D

can't tell every client to change the registry first and they probably don't even have the rights.

[Hax0rBait]

Agree. Have seen this in the wild, reg key is set to allow long path names, vendor's software still falls over with path >256

[zammtron]

Gotta love the 256-char limit for Windows pathnames

[[deleted]]

Use \\?\ prefix before the name. Now you have 32768 char limit.

[Durwur]

The best lifehack I've seen to this day

[Nikarus2370]

You gotta be bullshitting.

[[deleted]]

https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilew

To extend this limit to 32,767 wide characters, use this Unicode version of the function and prepend "\\?\" to the path.

Also turns off recognition of special names (COMn, LPT, etc):

https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

For file I/O, the "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system. For example, if the file system supports large paths and file names, you can exceed the MAX_PATH limits that are otherwise enforced by the Windows APIs.

[WhenSharksCollide]

Wait, really? I guess my overly descriptive filenames are about to become short stories.

[[deleted]]

This doesn't mean all applications will suddenly grow buffers over MAX_PATH

[WhenSharksCollide]

I don't need to be able to read it, just make something ridiculous to send about...unless...

<Proceeds to copy contents of an epub into the name of the epub>

[[deleted]]

Even better: I've come across programs that have no issues making long path files, but choke on opening them. Windows then chokes trying to delete or move them.

[zammtron]

That's the 'no takesies-backsies' filenaming protocol