Ah- I missed your post on April 28. Further thinking on the issue, I'm inclined to let the user specify a path to the executable as a configuration setting - or even include the major platform executables in the plugin - and just avoid burdening users with scripts.
Cheers, Stephen On Tuesday, August 24, 2010, Jakub Piotr Cłapa <jpc...@zenburn.net> wrote: > This came up before and the environment.plist is mentioned in many places as > the proper solution. It seems that Apple introduced /etc/paths.d for this but > you found that it is not sufficient for GUI apps. > > OTOH a simple (getenv "PATH") returns the same things as echo $PATH in a > Terminal window. Generally every environment variable I set in my .zshenv is > visible in DrRacket. (including all the paths from paths.d) > > PS. I run 10.6 and Racket 5.0.1.2--2010-07-26. > > -- > regards, > Jakub Piotr Cłapa > -- -- Stephen De Gabrielle stephen.degabrie...@acm.org Telephone +44 (0)20 85670911 Mobile +44 (0)79 85189045 http://www.degabrielle.name/stephen _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
