Emacs *inferior-lisp* process not starting

Emacs *inferior-lisp* process not starting

[Markus Arike]

Hi everyone,

I'm running Emacs 23.2 (cocoa version) on OSX which had worked 
flawlessly.  It is now broken.  I previously had Emacs, Slime, and 
OpenMCL or SBCL set-up perfectly for the past few weeks and have been 
loving life, studying Lisp code daily. Last night, in trying to install 
Quack for Scheme, I may have changed some of the Emacs Preferences 
regarding Lisp, Inferior Lisp (?).

Now the *inferior-lisp* process is not starting when I start emacs, nor 
can I start it by typing M-x run-lisp.  Typing 'M-x run-lisp' returns 
the error message:

"Can't exec program: /Applications/Emacs.app/Contents/MacOS/bin/env"

And where Emacs lists the open buffers, reads *inferior-lisp*   
[(Inferior Lisp:no process)].  Yikes.

All the Emacs versions on my Mac return the same error message, 
including GNU Emacs 22.1.1 (mac-apple-darwin) Terminal version.  It 
returns the same message but obviously with a different path:

"Can't exec program: /usr/libexec/emacs/22.1/mac-apple-darwin/env"

I think that *inferior-lisp* opened at startup previously and now, 
because of my silly tinkering, it does not.  Does anybody know how if 
this can be corrected?

I reinstalled Emacs, and it is the same story.  I must have made some 
global change that is effecting all my installed Emacs.  I started with 
a no .emacs file, and it is still broken.  Can anyone kindly offer me 
any advice on how I can restore my Emacs to it's pristine 
configuration?  Thanks so much.


Markus Arike
Troubled Emacs user.

Re: Emacs *inferior-lisp* process not starting

[Peter Dyballa]

Am 28.10.2010 um 03:15 schrieb Markus Arike:

> "Can't exec program: /Applications/Emacs.app/Contents/MacOS/bin/env"

You must have screwed up exec-path or such. The two env programmes you  
mention certainly don't exist at the given path names.

--
Greetings

   Pete

There's no place like 127.0.0.1
			– origin unknown

Re: Re: Emacs *inferior-lisp* process not starting

[Markus.Arike]

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

Actually I think they do. What I believe Emacs is doing is calling the env,  
much like a she-bang line like #!/usr/bin/env ruby, for example. I just  
can't figure out of which executable, as the programs in those directories  
are:

digest-doc* hexl* movemail* rcs2log* update-game-score*
fakemail* profile* sorted-doc* vcdiff*

For a temporary fix I made a symlink to /usr/local/bin/ccl64 and it sort of  
works how a freshly installed Emacs is configured. My question is this:  
Since this error that I noted in my original post is happening on all the  
version of Emacs on my system, is there a global "user preferences" file,  
other than a .emacs file, when a user edits his/her preferences via the  
Preferences menu?

Thanks a lot in advance for any clues as to what is going on.

Markus


On Oct 28, 2010 4:58am, Peter Dyballa <Peter_Dyballa@web.de> wrote:


> Am 28.10.2010 um 03:15 schrieb Markus Arike:




> "Can't exec program: /Applications/Emacs.app/Contents/MacOS/bin/env"




> You must have screwed up exec-path or such. The two env programmes you  
> mention certainly don't exist at the given path names.



> --

> Greetings



> Pete



> There's no place like 127.0.0.1

> – origin unknown





[-- Attachment #2: Type: text/html, Size: 1655 bytes --]

Re: Emacs *inferior-lisp* process not starting

[Peter Dyballa]

Am 28.10.2010 um 17:29 schrieb Markus.Arike@gmail.com:

> For a temporary fix I made a symlink to /usr/local/bin/ccl64 and it  
> sort of works how a freshly installed Emacs is configured. My  
> question is this: Since this error that I noted in my original post  
> is happening on all the version of Emacs on my system, is there a  
> global "user preferences" file, other than a .emacs file, when a  
> user edits his/her preferences via the Preferences menu?

Yes, there is: ~/.MacOSX/environment.plist. It sets the environment  
for all processes at boot time. Read more here: http://developer.apple.com/qa/qa2001/qa1067.html 
  (also available via Xcode on disk: /Developer/Documentation/DocSets/ 
com.apple.ADC_Reference_Library.CoreReference.docset/Contents/ 
Resources/Documents/qa/qa2001/qa1232.html).

The file can be used as in:

	setenv MANPATH	`defaults read ~/.MacOSX/environment MANPATH`
	export PATH=$(defaults read "${HOME}/.MacOSX/environment" PATH)


Since Mac OS X 10.5 Apple introduced /etc/paths.d and /etc/manpaths.d.  
There you can put files with the path to some additional bin or man  
directory. Both methods should be able to solve the problem that  
Aquamacs cannot find some executables.

--
Greetings

   Pete

Who the fsck is "General Failure," and why is he reading my disk?