News for hackers. Stuff that matters.

A comment on Bash Pitfalls. Parent comment

Re:Bash Pitfalls by JoshTriplett on Sunday August 16, 2015 @03:50PM (#10070038)
Alternatively, allow everything in filenames, including whitespace and '/', but escape them on the filesystem using something like URL escaping (%20, %2F). No reason the filesystem names have to match the user-friendly names precisely, as long as a lossless bidirectional conversion exists.
[ Parent | on HN ]
Re:Bash Pitfalls by frou_dh on Sunday August 16, 2015 @07:35PM (#10070696)
Neat idea. If I understand correctly, it'd still be fair to say that those characters wouldn't be allowed in file names since encoding/decoding the friendly form would be opt-in work each and every userspace program couldn't be relied upon doing?
[ Parent | on HN ]
Re:Bash Pitfalls by mitchty on Monday August 17, 2015 @01:48AM (#10071526)
Yep, the vfs layer in most unixes won't let you use / or \0 in a filename. And for good reasons.
[ Parent | on HN ]