Re: can one run tk/Ruby gui code from an emacs shell with compile?

[Peter Dyballa]

Am 19.11.2005 um 12:32 schrieb Anne G:

> I was worried that emacs might be using the ruby 1.6 which
> comes as a default on panther, so I deleted two folders that
> had 1.6 in it, and checked terminal still runs my snipet.

There is an "easy" way to correct the system when it constantly uses  
the wrong binary: change the search path, i.e. the PATH variable in  
bash or path in tcsh. To do so invoke in some shell 'which programme  
name', i.e. 'which ruby'. The answer might be /bin/ruby. So you now  
know that /bin should come later in PATH or path. For bash you can  
change in ~/.bashrc (which is always executed when bash is launched)

        export PATH="<home of new ruby>:$PATH"

for tcsh there is .tcshrc:

        set path=(<home of new ruby> $path)

> The DLY directory line seems permanently removed.

That's what you think! Just try this: M-x shell-command <RET> env |  
sort <RET>! And then look (search) for DYLD_LIBRARY_PATH. It's still  
there, isn't it? The runtime environment, in which Carbon Emacs  
executes, still has this variable set. Any process that is spawned by  
Emacs, for example a compilation, inherits this environment. Try to  
rename (or remove) these two  
/Applications/Emacs.app/Contents/Resources/share/emacs/22.0.50/site- 
lisp/site-start.d/carbon-emacs-builtin-aspell.el* files! In Carbon  
Emacs it's very easy to access the interiors of an application bundle.

To check whether things are right in Carbon Emacs' runtime environment  
you can use this: M-! env | egrep -w 'PATH|DYLD_LIBRARY_PATH' (the  
short version).

For those graphical Mac OS X applications there is (almost?) no other  
way then ~/.MacOSX/environment.plist to prepare them with a suitable  
runtime environment. Once you have created that file (in the Developer  
Tools there is a Property List Editor which is automagically launched  
when you invoke in a shell 'open ~/.MacOSX/environment.plist'), it  
probably works at once when you invoke an application newly. And it  
changes the runtime environments for all applications too, once they've  
been re-launched!

Read Apple's http://developer.apple.com/qa/qa2001/qa1067.html!

--
Greetings

  Pete

Mac OS X is like a wigwam: no fences, no gates, but an apache inside.