Alexander Burger <a...@software-lab.de> writes:

Hi Alex,

>> I have a problem there, I tried
>> 
>> ,--------------------------------
>> | home/tj1/bin/picolisp/pil       |
>> | home/tj1/bin/picolisp/plmod     |
>> | home/tj1/bin/picolisp/bin/pil   |
>> | home/tj1/bin/picolisp/bin/plmod |
>> | home/tj1/bin/picolisp/bin/psh                             |
>> `--------------------------------
>> 
>> but no matter which one  I use, and I always get an error, e.g. 
>> 
>> ,--------------------------------------------------------------
>> | (prog (load                                                  
>> | "/home/tj1/bin/picolisp/lib/swank-picolisp/swank-picolisp.l")
>> | (swank-start "/tmp/slime.20688"))                            
>> |                                                              
>> | Can't exec program:                                          
>> | /home/tj1/bin/picolisp/bin/psh                               
>> `--------------------------------------------------------------
>> 
>> Now I'm a bit confused - which command should I use, and is that related
>> to file permissions (they seem alright to me) or something else?
>
> I think this error occurs because the binary 'picolisp' cannot be found.

strange, I changed $PATH and emacs exec-path:

,-------------------------------------------------------------------------------------------
| ~ $ echo $PATH                                                                
            
| 
/home/tj1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
    
| 
/usr/local/scala/bin:/home/tj1/shellscripts:/home/tj1/.cabal/bin:home/tj1/bin/picolisp/bin
`-------------------------------------------------------------------------------------------

,--------------------------------------------------------------------
| ~ $ (print exec-path)                                              
| ("/home/tj1/shellscripts" "/home/tj1/bin" "/usr/local/sbin"        
| "/usr/local/bin" "/usr/sbin" "/usr/bin" "/sbin" "/bin" "/usr/games"
| "/usr/local/scala/bin" "/usr/lib/emacs/23.1/i686-linux-gnu"        
| "/home/tj1/.cabal/bin/" "/home/tj1/" "/home/tj1/bin/picolisp/bin") 
`--------------------------------------------------------------------
 
and still get the same error message:

,--------------------------------------------------------------
| (prog (load                                                  
| "/home/tj1/bin/picolisp/lib/swank-picolisp/swank-picolisp.l")
| (swank-start "/tmp/slime.1757"))                             
| Can't exec program:                                          
| /home/tj1/bin/picolisp/pil                                   
|                                                              
| Process inferior-lisp exited abnormally with code 1          
`--------------------------------------------------------------



> BTW, 'psh' does not make sense to be executed stand-alone (though this
> is not the problem here), because it tries to connect to a running
> PicoLisp application server.

ok, I changed that to 'pil'

> But "/home/tj1/bin/picolisp/pil" or "/home/tj1/bin/picolisp/plmod", for
> example, should work, if in the directory "/home/tj1/bin/picolisp/bin" a
> binary executable "picolisp" can be found.

and there is an executable 'picolisp' in "/home/tj1/bin/picolisp/bin"
(and without slime, with inferior picolisp mode, it works)

,-------------------------------------------------------
| /home/tj1/bin/picoLisp/bin:                           
| insgesamt 232                                         
| drwxr-xr-x  2 tj1 tjx   4096 2011-11-11 15:23 .       
| drwxr-xr-x 19 tj1 tjx   4096 2011-11-15 01:35 ..      
| -rwxr-xr-x  1 tj1 tjx 206636 2011-11-11 15:23 picolisp
| -rwxr-xr-x  1 tj1 tjx    107 2010-03-14 16:37 pil     
| -rwxr-xr-x  1 tj1 tjx    223 2011-05-30 07:56 plmod   
| -rwxr-xr-x  1 tj1 tjx    277 2011-05-06 08:14 psh     
| -rwxr-xr-x  1 tj1 tjx    923 2011-05-06 08:45 replica 
| -rwxr-xr-x  1 tj1 tjx   2211 2008-03-09 15:16 watchdog
`-------------------------------------------------------

When using slime, should the inferior buffer a *inferior-lisp* or rather
a *inferior-picolisp* buffer? I guess, the *inferior-lisp* buffer should
be fine ...

Cheers,
-- 
Thorsten

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to