| |||||||||||||
Wheeler: Fixing Unix/Linux/POSIX FilenamesWheeler: Fixing Unix/Linux/POSIX FilenamesPosted Mar 25, 2009 15:32 UTC (Wed) by drag (subscriber, #31333)In reply to: Wheeler: Fixing Unix/Linux/POSIX Filenames by rsidd Parent article: Wheeler: Fixing Unix/Linux/POSIX Filenames
Uh. Wow.
Maybe if Linux folks keep identifying and fixing legacy Unix usability issues people will start referring to Linux as 'The way Unix should of been' or 'Unix done right'.
I am always really paranoid about file names in Linux when doing scripting or whatnot. It's difficult and dealing with them is always a "oh god I hope I did the escaping right" sort of deal. Because I know I can have a script that I use for lots of stuff, but sometime I may make a goober'd up filename late at night or something that can end up destroying data unless I did things exactly correct in my scripts.
Filenames with ~ in them, or < > or () or all sorts of odd things I make by mistake.
(Log in to post comments)
Wheeler: Fixing Unix/Linux/POSIX Filenames Posted Mar 25, 2009 16:20 UTC (Wed) by epa (subscriber, #39769) [Link] Maybe if Linux folks keep identifying and fixing legacy Unix usability issues people will start referring to Linux as 'The way Unix should of been' or 'Unix done right'.I thought that was Plan 9...
Wheeler: Fixing Unix/Linux/POSIX Filenames Posted Mar 25, 2009 22:14 UTC (Wed) by jordanb (guest, #45668) [Link]
While I'm not entirely sure what "Unix done right" is, but I *am* sure that a system where you get to choose between ed, sam, and acme isn't it.
|
|||||||||||||