this post was submitted on 27 Jul 2023
463 points (89.4% liked)
Technology
58303 readers
11 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unbelievably, Windows still has a ridiculously short filepath length limit.
Nope, long paths are supported since 8.1 or 10 person bit you have to enable it yourself because very old apps can break
Furthermore, apps using the unicode versions of functions (which all apps should be doing for a couple decades now) have 32kb maximum character length paths.
Thatβs not an NTFS issue. Thatβs a Windows issue.
That's not even a Windows issue, that's an issue with specific Win32 API.
Are you writing parahraphs for folder/file names? That's one "issue" I never had problem with.
Maybe enterprises need a solution for it but that's a very different use case from most end users.
Improvements are always welcome but saying it's "ridiculously short" makes the problem sound worse than it is.
I think they mean the full path length. As in you can't nest folders too deep or the total path length hits a limit. Not individual folder name limits.
File paths. Not just the filename, the entire directory path, including the filename. It's way too easy to run up against limit if you're actually organized.
It might be 255 characters for the entire path?
I've run into it at work where I don't get to choose many elements. Thanks "My Name - OneDrive" and people who insist on embedding file information into filenames.
The limit was 260. The OS and the filesystem support more. You have to enable a registry key and apps need to have a manifest which says they understand file paths longer than 260 characters. So while it hasn't been a limitation for awhile, as long as apps were coded to support lesser path lengths it will continue to be a problem. There needs to be an conversion mechanism like Windows 95 had so that apps could continue to use short file names. Internally the app could use short path names while the rest of the OS was no longer held back.
32k Unicode characters. No, mate, it's not easy to run up.
You like diving 12 folders deep to find the file you're after? I feel like there's better, more efficient ways to be organized using metadata, but maybe I'm wrong.
Not OP, but I occasionally come across this issue at work, where some user complains they they are unable to access a file/folder because of the limit. You often find this in medium-large organisations with many regions and divisions and departments etc. Usually they would create a shortcut to their team/project's folder space so they don't have to manually navigate to it each time. The folder structure might be quite nested, but it's organized logically, it makes sense. Better than dumping millions of files into a single folder.
Anyways, this isn't actually an NTFS limit, but a Windows API limit. There's even a registry value[1] you can change to lift the limit, but the problem is that it can crash legacy programs or lead to unexpected behavior, so large organisations (like ours) shy away from the change.
C:\Users\axexandriaanastasiachristianson\Downloads\some_git_repo\src\...You run into the file parth limit all the fucking time if you're a developer at an organization that enforces fullname usernames.
I think I've spotted the real problem.
People have been talking about the real problem from the beginning of the thread: small character limit on file paths.
The limit is 32,000 characters.
Only if you go into settings, disable the safety measures and change it. And some apps might break.
No, the default file path limit is 256 characters. And I donβt mean file name. Full file path.
No, you don't need to change any settings, that's the thing! Windows, unlike other OSes, has several APIs. Old apps (and dumb apps) are using old API and are limited to 260 characters. New apps are using new API and are limited by 32k characters. This "new API" is available since NT4, btw.
I remember I had to change a setting when using Windows. And it even showed me an βAre you sure?β dialog. It wasnβt that long ago. Is that not a thing anymore?
Once again, that only affects old or dumb apps. Any half decent app supports 32k paths since late 1990-s.
I would be pissed if they made me use such a ridiculously long login name at work. Mine is twelve characters and that's already a pain in the ass (but it's a huge company and I have a really common name, so I guess all the shorter variations were already taken).
Edit: Also, I checked it's really very simple to enable 32kb paths in recent versions of Windows.
If your name consists of non-ASCII characters, like Thai words or Arabic or Chinese, it's pretty easy to rack up >15 bytes in your username alone.
Metadata is slow, messy, and volatile. Also, shortcuts are a thing.