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


Click here to return to the '10.5: Create executable command-line AppleScripts' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Create executable command-line AppleScripts
Authored by: jubalkessler on Feb 11, '09 01:53:11PM

I completely disagree with any suggestions of leaving off a file extension for OSA scripts. Let me put it this way. When viewing files on the commandline -- or even in Finder view -- it's impossible to tell what kind of script it is unless (a) it's been typed by the OS via type/creator codes, which is deprecated IIRC, and (b) file extensions. One could also look inside the file, but that's tedious on a large scale.

So if I'm looking at ten or twenty scripts, half of which are Bourne shell (.sh) and the other OSA, then I definitely want to differentiate based on filename.

There's nothing wrong with using filename extensions, and it's good practice to use ones that are commonly agreed (as much as possible, anyway) to represent, and only represent, AppleScript scripts.

So perhaps .scpt after all.



[ Reply to This | # ]