I'm trying to get ilisp working on Mac OS X 10.1.5, with only partial
success. My experience with Emacs is pretty limited, so I'm not entirely
sure whether my difficulties are actually with ilisp and not Emacs
configuration. FWIW, I haven't used ilisp at all to this point.
The general behavior I'm seeing is that ilisp works when I run run Emacs
in Terminal, but doesn't work properly in one of the more graphical Emacs
versions out there. I've tried the Carbon version of Emacs 21.1 from
<http://www.porkrind.org/emacs> and the Cocoa version
<http://sourceforge.net/projects/emacs-on-aqua> as well. For each of
these, I can M-x then enter 'run-ilisp'. I get asked for the dialect, and
that's where things go wrong. Whether I enter either 'openmcl' or
'clisp-hs', I get a response of 'Searching for program: no such file or
directory, xxx', where xxx is the dialect name. As mentioned before, the
same procedure works fine for Emacs in a Terminal window.
For compiling ilisp, I have tried setting EMACS=emacs and
EMACS=/Applications/Emacs.app/Contents/MacOS/Emacs in the Makefile (as
well as a variety of other things that simply didn't compile!). Behavior
is the same in each case.
Does anyone have any suggestions? Does this seem like a problem with Emacs
or with ilisp?
--
Michael J. Barber
········@ascc.artsci.wustl.edu (Michael James Barber) writes:
> Does anyone have any suggestions? Does this seem like a problem with Emacs
> or with ilisp?
It sounds like a problem with your paths, as Marco said. I assume
that OpenMCL is in your path from the Terminal, but if you run Emacs
from the Finder, then it's going to inherit its environment from
there. Try opening Emacs from the Terminal, and see if that works.
Incidentally, now that X11 is super-easy to install for OS X (Apple's
X11.app is a breeze), you might try running Emacs with X11 support.
Then, it's the same old emacs you (may have) had on Unix, with the
lovely ability to display windows remotely. Of course, if you have no
desire to do that, then you may as well stick with Carbon or Cocoa
Emacs (assuming they're stable now).
--
/|_ .-----------------------.
,' .\ / | No to Imperialist war |
,--' _,' | Wage class war! |
/ / `-----------------------'
( -. |
| ) |
(`-. '--.)
`. )----'
···@mudslide.OCF.Berkeley.EDU (Thomas F. Burdick) writes:
> ········@ascc.artsci.wustl.edu (Michael James Barber) writes:
>
> > Does anyone have any suggestions? Does this seem like a problem with Emacs
> > or with ilisp?
>
> It sounds like a problem with your paths, as Marco said. I assume
> that OpenMCL is in your path from the Terminal, but if you run Emacs
> from the Finder, then it's going to inherit its environment from
> there. Try opening Emacs from the Terminal, and see if that works.
From the Mac README file of the Emacs distribution:
+ On Mac OS X, environment variables are not set up correctly when
Emacs is started from the Finder.
See <http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/mac/README?rev=1.6&content-type=text/vnd.viewcvs-markup>
Looks like this still isn't fixed.
Edi.
Edi Weitz <···@agharta.de> writes:
> From the Mac README file of the Emacs distribution:
>
> + On Mac OS X, environment variables are not set up correctly when
> Emacs is started from the Finder.
>
While we are waiting for this to be fixed, and indeed waiting to find
out what correctly set up is (I don't know, I would have thought that it
inherits the environment correctly now, unfortunately the inherited
environment is rather poor). There is a way to set the environment
for the loginwindow and thus the Finder and the programs started from
the Finder.
Configure ~/.MacOSX/environment.plist
I used to have a link to a Apple document for this, but it is no
longer working. Perhaps you can search for
BootingLogin/Customization_Techniques.html
//Lennart
Lennart Staflin <·····@lysator.liu.se> writes:
> Edi Weitz <···@agharta.de> writes:
>
> > From the Mac README file of the Emacs distribution:
> >
> > + On Mac OS X, environment variables are not set up correctly when
> > Emacs is started from the Finder.
> >
>
> While we are waiting for this to be fixed, and indeed waiting to find
> out what correctly set up is (I don't know, I would have thought that it
> inherits the environment correctly now, unfortunately the inherited
> environment is rather poor). There is a way to set the environment
> for the loginwindow and thus the Finder and the programs started from
> the Finder.
>
> Configure ~/.MacOSX/environment.plist
Thanks for this info. Currently I can only get my hands on OS X when
my wife is giving me her old Pismo PowerBook for a couple of hours but
I'm trying to follow just in case I might buy a new PB in the next
months... :)
> I used to have a link to a Apple document for this, but it is no
> longer working. Perhaps you can search for
> BootingLogin/Customization_Techniques.html
It's now at:
<http://developer.apple.com/techpubs/macosx/Essentials/SystemOverview/BootingLogin/chapter_4_section_15.html>
Edi.
Hi
are you sure your paths are ok? It just seems like the Emacs you are
using is not setting them up correctly.
In particular, what are the values of `openmcl-program' etc etc?
Cheers
marco
Michael James Barber wrote:
> I'm trying to get ilisp working on Mac OS X 10.1.5, with only partial
> success. My experience with Emacs is pretty limited, so I'm not entirely
> sure whether my difficulties are actually with ilisp and not Emacs
> configuration. FWIW, I haven't used ilisp at all to this point.
>
> The general behavior I'm seeing is that ilisp works when I run run Emacs
> in Terminal, but doesn't work properly in one of the more graphical Emacs
> versions out there. I've tried the Carbon version of Emacs 21.1 from
> and the Cocoa version
> as well. For each of
> these, I can M-x then enter 'run-ilisp'. I get asked for the dialect, and
> that's where things go wrong. Whether I enter either 'openmcl' or
> 'clisp-hs', I get a response of 'Searching for program: no such file or
> directory, xxx', where xxx is the dialect name. As mentioned before, the
> same procedure works fine for Emacs in a Terminal window.
>
> For compiling ilisp, I have tried setting EMACS=emacs and
> EMACS=/Applications/Emacs.app/Contents/MacOS/Emacs in the Makefile (as
> well as a variety of other things that simply didn't compile!). Behavior
> is the same in each case.
>
> Does anyone have any suggestions? Does this seem like a problem with Emacs
> or with ilisp?
>
>
In article <··········@ascc.artsci.wustl.edu>,
Michael James Barber <········@ascc.artsci.wustl.edu> wrote:
>I'm trying to get ilisp working on Mac OS X 10.1.5, with only partial
>
>The general behavior I'm seeing is that ilisp works when I run run Emacs
>in Terminal, but doesn't work properly in one of the more graphical Emacs
>
Problem resolved!
As several of you pointed out, it was a problem with my PATH variable.
Running Emacs from the Terminal put the path in there correctly, so that
the openmcl program was reachable, but the Carbon Emacs ignores my .cshrc
so that it couldn't find openmcl.
The fix may be trivial for a lot of readers, but since other Emacs novices
may have run into the same problem I did, I'll summarize the key points of
how to resolve things:
1) You can check the path that Emacs sees by entering (insert (getenv
"PATH")) into the scratch buffer, then C-x C-e. That should let you see
if it is just a path problem of not.
2) A quick and easy fix is to run Emacs from the Terminal. You can do
this with 'open -a Emacs' in a Terminal window. That may be enough of a
fix for many.
3) A more complete fix is to define your path in the file
~/.MacOSX/environment.plist so that you can run Carbon/Cocoa Emacs like
any other app. Rather than describe the procedure here, I'll just suggest
<http://www.astro.washington.edu/owen/AquaEnvVar.html> as a clear and
straightforward summary.
Thanks again to those who responded. You've been very helpful.
--
Michael J. Barber