16 Dec
2011
16 Dec
'11
8:43 a.m.
Cameron Kaiser wrote:
OS X is not Unix in this case and Unix never ever decided what to do with a
file by its extension but t does by its magic number (look for /etc/magic).
BTW:
touch what.the.heck.for.an.ext.tension.do.you.mean.?
$ ls -l what*
-rw-r--r-- 1 holm holm 0 16 Dez 17:40 what.the.heck.for.an.ext.tension.do.you.mean.?
$ rm what*
$
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741
Extensions are
extensions. All the above is just interpretation. File
association is not rocket science (though it's been reinvented too many
times). The interesting exception is classic MacOS with its type/creator
codes independent of extension (and where extensions were initially
absent, though like Unix, supported as part of the file name).
I have always loved type/creator codes, and was very unhappy with Apple for
removing them in 10.6 (but I'm 10.4 forever, so I guess it's not really my
concern).
The gap was that the core OS did not provide an easy way to manipulate this
consistently, requiring a cavalcade of minitools (or a trip to ResEdit) to
set them the way you wanted. But I loved being able to force certain files to
automatically open in different apps if I wanted to, and at least for a time
OS X gave you the choice.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- Nothing recedes like success. -- Walter Winchell ---------------------------