Re: [MACTCL] Problems running wish from a shell

[Jack J. <Jac...@or...>]

On Tuesday, February 5, 2002, at 06:52  PM, Ruediger Goetz wrote:

> Hello,
>
> O.K.
> I followed your suggestions.
> Here is what I found out (I didn't  synced to the CSV, yet)
>
> I have Wish Shell.app in /Applications  and I could start it 
> from the Finder,
> Hence I don't assume that there is something wrong with th permission..
> I have /usr/bin/wish beeing a hardlink to
> /Applications/Wish\ Shell.app/Contents/MacOS/Wish| Shell.

Bingo!

The hardlink is the problem. Whereas a symlink (or a MacOS 
alias, to a lesser extent) is really only a pointer to the 
destination filename a hardlink is something different: both 
hardlinks to the file (the original one and the one you put in 
/usr/bin/wish) have the same "status" for the OS. So, if you 
execute the program by its /usr/bin/wish name there is no 
linkage to the surrounding .app framework.

You could try replacing the hardlink with a symlink, but I 
wouldn't bet the farm on that working either. The wish 
application will still get /usr/bin/wish as its  argv[0], and 
whether it [*] is smart enough to follow symlinks to find the 
real location of the binary, and hence the .app magic, remains 
to be seen. [*] note that "it" here refers to the hypothetical 
Carbon.framework or whatever code that determines we're running 
from a .app framework, not to the wish main program.

If the symlink doesn't work a two-liner such as this will:
#!/bin/sh
exec "/Applications/yaddayaddayadda/Wish Shell" $@
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -