Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Excerpt! | 12 comments | Create New Account
Click here to return to the 'Excerpt!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Excerpt!
Authored by: K3nt on Mar 31, '02 08:32:14AM

Here's what "MacOS X: The Missing Manual" states about file naming conventions in MacOS X.

" You can use letters, numbers, punctuation - in fact, any symbol you want except for the colon ( : ), which the Mac uses behind the scenes for it's own folder-hierarchy designation purposes."

" Note: You can't use a period or slash, either, if it BEGINS a filename."

(Own addition, .filename are unix-hidden files so, yes you can use a . as a filename start but then the end result will be a hidden file.)

Have fun!



[ Reply to This | # ]
Linux explanation
Authored by: saint.duo on Mar 31, '02 09:08:19AM

I remember a Linux using friend of me explaining it to me this way, a few years ago, when we were talking about naming files. Basically, he said that I could name a file almost anything I wanted, but if I used / or a period in the name, that I may have trouble working with the file in the command line, if I didn't watch what I was doing. He also stated that scripts that don't explicitly quote path names would have troubles with this as well. Well, the program wouldn't, but my results might. Think about the iTunes updater that killed volumes. That was due to not quoting the path in the program...



[ Reply to This | # ]