Of course, the way to fix *nix filenames in the first place is, well, not to use a ham-fisted definition of filenames in the first place.
But that would be too difficult. Also, it abrogates Freedom. In this specific case, it abrogates the freedom to use spaces in filenames, which (for some ungodly reason, possibly to do with the real world) users want.
Bit of a bugger when your entire shell pipeline depends upon a stream-o-bytes, innit?
“It’d be easier and cleaner to write fully-correct shell scripts if filenames couldn’t include any kind of whitespace. There’s no reason anyone needs tab or newline in filenames, as noted above, so that leaves us with the space character.”
On the one hand, this is difficult to argue with. You can’t argue with comparatives (or, if you prefer, Boolean logic).
On the other hand, it’s insane.
There’s no such thing as a “fully-correct” shell script. How could there be? There’s no goddamn grammar for the things.
And there’s no good reason to eliminate whitespace in a file name, unless you are also going to eliminate, say, the bottom 32 characters of the ASCII alphabet … which *nix signally fails to do.
When will these retards grow a brain?
Comments
Oldie but goldie http://tmrepository.com/fudtracker/no-sharp-edges/
Guess we need some kind of search over FUDs too
I don’t think it’s a good idea to mandate encodings on file names. Windows doesn’t do that either. Instead it uses UTF-16 on FS level, but what you use for the filename is your choice. You can use UTF-16, UTF-8 or even encodings as you wish. That approach is more flexible also.
“Oldie but goldie http://tmrepository.com/fudtracker/no-sharp-edges/
Guess we need some kind of search over FUDs too”
An anti-double post protection by checking whether a FUD with the URL already exists might be suitable, too.
You must be signed in to leave comments.