# sorry, I didn't reply to the list<br><br><div class="gE iv gt"><table class="cf gJ" cellpadding="0"><tbody><tr><td class="gF gK"><table class="cf ix" cellpadding="0"><tbody><tr><td></td></tr></tbody></table></td><td class="gH">
</td><td class="gH"></td></tr></tbody></table></div>I use racket with M-x run-scheme not slime.<br><br>compiling
is definetly overkill, but I'm not sure the parameters are
incompatible. There's a lot of application on OS X that uses the same
structure as on unix/linux.<br><br><br><div class="gmail_quote">2011/7/14 Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">9 hours ago, John Clements wrote:<br>
> On Jul 13, 2011, at 8:19 PM, Lavoie Francis wrote:<br>
</div><div class="im">> > I want to learn racket. I already started learning lisp from Land<br>
> > of Lisp, Practical Common Lisp and a bit of Clojure.<br>
> ><br>
> > For my everyday job (python, javascript) I use emacs, to learn<br>
> > lisp and clojure I used emacs with slime. I would like to do the<br>
> > same thing with racket but I ran into trouble, emacs can't find<br>
> > racket.<br>
> ><br>
> > First, it looks like emacs for OS X does not use the users' own<br>
> > $PATH, but the one of the system. I tried some hack I found on<br>
> > google<br>
> > (<a href="http://olabini.com/blog/2009/12/path-problem-with-emacs-on-mac-os-x/" target="_blank">http://olabini.com/blog/2009/12/path-problem-with-emacs-on-mac-os-x/</a>,<br>
> > <a href="http://www.emacswiki.org/emacs/EmacsApp#toc2" target="_blank">http://www.emacswiki.org/emacs/EmacsApp#toc2</a>) without luck, emacs<br>
> > can't find racket.<br>
><br>
> This one I can shed some light on. If you start emacs (or any other<br>
> program) from a shell (running in a terminal window), it inherits<br>
> that shell's PATH. If you start it from the finder, though, it<br>
> doesn't. One way to fix this is to start emacs from a terminal<br>
> window. Another is to try a hack such as the one you describe.<br>
> Another one is to explicitly specify the path in the command that<br>
> runs racket.<br>
<br>
</div>Given that confusion, and the fact that most people on OSX use the<br>
finder to run things, the last option is probably the most convenient.<br>
Note, however, that slime won't work with racket.<br>
<br>
Another option is to put symlinks in whatever is in your Finder's<br>
default $PATH.<br>
<div class="im"><br>
<br>
> > So I tried to compile racket from source.<br>
<br>
</div>(That's definitely an overkill for solving a $PATH problem...)<br>
<div class="im"><br>
> > I used the unix build to install racket into the standard path.<br>
> >> ./configure --enable-mac64 --enable-xonx --prefix=/usr/local<br>
> > It produced the following error message: --enable-mac64 and<br>
> > --enable-xonx are not valid option; but everything runs well and<br>
> > works! Great I can start to create some stuff.<br>
<br>
</div>They are definitely not compatible -- the first is for OSX<br>
applications (whatever buzzword is used (cocoa?)), and the second is<br>
for a unix build that uses the OSX X thing.<br>
<br>
Also, note that by default -- without a `--prefix' flag, Racket builds<br>
itself in place. When that's done you can move the resulting<br>
directory anywhere you want. It's generally much more conveinent than<br>
`--prefix'.<br>
<font color="#888888"><br>
--<br>
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:<br>
<a href="http://barzilay.org/" target="_blank">http://barzilay.org/</a> Maze is Life!<br>
</font></blockquote></div><br>