Re: BUG: Where's Application Support?
Re: BUG: Where's Application Support?
- Subject: Re: BUG: Where's Application Support?
- From: Paul Berkowitz <email@hidden>
- Date: Sun, 16 Jun 2002 07:29:52 -0700
On 6/16/02 2:43 AM, "Richard Morton" <email@hidden> wrote:
>
On Sunday, June 16, 2002, at 05:31 PM, Paul Berkowitz wrote:
>
> path to application support folder from user domain
>
>
>
> (with 'folder' included) also errors here. This time 'folder' is the
>
> offending word following the variable 'support'. Still no good.
>
>
Just a hunch - do you have Smile/Satimage installed? I had this happen
>
to me under OS 9 because of the osax, IIRC.
Yes indeed. Excellent hunch.
The Satimage osax has a term
path to application
which is evidently taking precedence when
path to (application support)
is not parenthesized. A namespace conflict in OS X already! That would
explain why Philip didn't need to do this whereas John and I do need to do
so. And of course, so may anybody's users, even if a script author does not
have Satimage installed and does not no anything about this conflict.
Tsk, tsk, Emmanuel. ;-) Maybe before too many people have got going with OS
X osax scripting, 'path to application' could be changed to 'path of
application' with the same <<event SATIAPPL>> raw code?
In the meantime, everyone should be aware that you had better use either
path to (application support)
or
path to "asup"
in your scripts not to cause a problem for users who have Satimage
installed. I am releasing some new scripts which require Satimage for its
excellent 'convert to Mac' and 'convert to Windows' commands. That may
inadvertently break other people's scripts which call 'path to application
support'.
<<event earsffdr>> application support
compiles correctly once, but re-compiles with the error once the English
word 'application' has appeared, of course.
You could go also whole hog with
<<event earsffdr>> "asup"
For some reason
<<event earsffdr>> <<constant asup>>
won't compile at all when it hits <<constant asup>>. Does anyone know why
<<constant xxxx>> doesn't want to compile, even on its own?
(Throughout, << >> are being used here to avoid list server mangling when
guillemets made by option-\ and option-shift--\ on US keyboards are typed. I
guess this is never, ever going to fixed? Idiotic.)
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.