On 06/25/11 at 03:20pm, Scott Ferguson wrote: > On 25/06/11 10:16, lee wrote: > > Scott Ferguson <prettyfly.productions@gmail.com> writes: > > > >> I don't think the "no white spaces" and "no accented characters" > >> "rule" is valid in the 21st century. But if some one can put up an > >> authoritative, and recent, reason I'll reconsider. > > > > Since (unfortunately) there isn't anything preventing users from > > creating files with names that contain special characters or spaces, you > > could say that there isn't such a rule anymore. > > There is... > > > > > Nonetheless I advise against it, very un-authoritatively of course, > > because it can be troublesome to create files with special characters or > > spaces in their names. > > > > To give a silly example, a file named "-rf *" or "rm -rf *" > > I defy you to create a file with those name ;-p > NOTE: I've tried. No point in it just being an untested opinion. Why wouldn't you be able to? None of those are forbidden characters for filenames. ,---------------------------- |liam@slimer:~/safe$ touch ./-rf\ * |liam@slimer:~/safe$ ls |-rf * `--------------------------- -- Liam
Attachment:
signature.asc
Description: Digital signature