>windows

>windows
>probably is clearly your filesystem. Windows can read the file just fine.

>use linux
>put space in filename
>computer shits itself and sprays sparks

>>60176861
I have tons of spaces in the filenames of things I installed thru wine

>>60176841
filename clearly isnt long, so its probably whatever director(ies) its stored in.

>>60176861
>probably is clearly your filesystem. Windows can read the file just fine.
and who do you think made that filesystem? da jooz?

File: 1480969578927.jpg (37KB, 600x338px) Image search: [Google]

37KB, 600x338px

>>60176841
>professional grade OS
>can't handle long filenames/folders
AHAHAHAHAHAH

>try moving to a location with a shorted path name
gives the same error wat do?

>>60176841
Linux also has this problem if your path name is long enough.

>>60178535
Except on Linux that's two different things.
The maximum file name length is 255, but the maximum path name length is 4096, which should be more than enough.
You can also change the limits in the source and recompile the kernel, but it might break something.

>when the files so lomg that it wont lwt you rename it or delete it
happened to me on several occasions.

>>60176841
>W**dows
Found your problem

>>60178526
install dos and use 8.3 names

>>60176861
I have plenty of filenames with spaces in them. It just makes the files a bit more cumbersome to manipulate in bash, that's all.

>>60176841
There's a windows feature with windows 10 update that allows for longer filenames (aka bigger then 260 characters).
It was an old limitation restricted only by the OS as the NTFS file system always allowed long ass names.

>>60181083
forgot this
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/

>>60176861
You can put fucking newlines and backslashes in Linux filenames