Skip to main content
5 events
when toggle format what by license comment
Apr 13, 2017 at 12:36 history edited CommunityBot
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Jan 28, 2013 at 3:42 vote accept naught101
Jan 27, 2013 at 13:30 comment added njsg Which other character would you suggest we standardize in? The only character that would not be accepted in filenames at the filesystem level is NULL. And that would break almost everything which does string manipulation.
Jan 27, 2013 at 13:16 comment added Bonsi Scott Nice one, but i don't agree with spaces in filenames. If scripts can't deal with it, they have to be fixed and not the filenames themselves.
Jan 27, 2013 at 10:49 history answered njsg CC BY-SA 3.0