Long File Paths
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
It appears that fman does not support long file paths. I'm using Windows 10 64bit and long file paths are enabled.
Although Windows Explorer and Fman can't handle these, Total Commander can handle them just fine, so there's no doubt that support for long file paths is indeed enabled and supported at the OS level.
Use Case 1: When attempting to copy a directory that contains a hierarchy of directories that result in a long file path (probably the limit is 255 chars?) this operation results in the error shown in the attached image.
Use Case 2: When attempting to browse deep into a hierarchy that results in a long file path, the user can only browse as deep as the limit (probably 255 chars?) and then the next directory in the hierarchy is displayed but not accessible, meaning that double-clicking on pressing the Enter key while the directory is selected in fman doesn't do anything.
Error for use case 1(copy long paths): 
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing both reported cases on Windows 10: copying a directory with a long hierarchy and browsing into a deep hierarchy in fman. Trace the file-copy and directory-navigation entry points involved in those operations, then verify that paths beyond the reported limit can be copied and opened without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100