Re: [STUMP] How to make `C-t !' take my own executables into account?

[Bastien]

Shawn Betts <address@hidden> writes:

> C-t ; copy-last-message

Ok, it works.

C-t ; version 
  => 0.9.6-git

But now C-t : (getenv PATH) gives:

,----
| The variable PATH is unbound.0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) 
{B95E9FD}>)[:EXTERNAL]
| 1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {B95E9A9}>)
| 2: (STUMPWM::BACKTRACE-STRING)
| 3: (ERR "~A")[:EXTERNAL]
| 4: (STUMPWM::EVAL-LINE "(getenv PATH)")
| 5: (STUMPWM::CALL-INTERACTIVELY
|     "eval"
|     #S(STUMPWM::ARGUMENT-LINE :STRING "eval" :START 5))
| 6: (STUMPWM::EVAL-COMMAND "eval" T)
| 7: ((LABELS #:G319) :CODE 28 :STATE 4)
| 8: (STUMPWM::HANDLE-EVENT)[:EXTERNAL]
| 9: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
| 10: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]508))
| 11: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK
|      #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {B78A4CB5}>
|      #S(SB-THREAD:MUTEX
|         :NAME "CLX Event Lock"
|         :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {B40F559}>
|         :STATE 1))
| 12: (XLIB:PROCESS-EVENT #<XLIB:DISPLAY :0 (The X.Org Foundation 
R10600000)>)[:EXTERNAL]
| 13: (STUMPWM::STUMPWM-INTERNAL-LOOP)
| 14: (STUMPWM::STUMPWM-INTERNAL-LOOP)[:EXTERNAL]
| 15: (STUMPWM::STUMPWM-INTERNAL ":0")
| 16: (STUMPWM ":0")
| 17: ((LAMBDA ()))
| 18: ((LABELS SB-IMPL::RESTART-LISP))
`----

>> But (getenv PATH) returns the paths and they look fine (i.e. they
>> include my ~/bin/ directory.)
>
> The exact text is important as I hope to use it to try and reproduce
> it here.

I don't have it anymore...

>> One thingy: I first installed cl-ppcre via asdf-install, but I couldn't
>> compile stumpwm until I installed cl-ppcre via apt-get.  So maybe there
>> is something about my SBCL install that doesn't know about my home?
>
> That's odd. from stumpwm do:
>
> C-t : asdf:*central-registry*

,----
| ((MERGE-PATHNAMES ".clc/systems/" (USER-HOMEDIR-PATHNAME))
|  (MERGE-PATHNAMES ".sbcl/systems/" (USER-HOMEDIR-PATHNAME))
|  (LET ((ASDF::HOME (SB-EXT:POSIX-GETENV "SBCL_HOME")))
|    (WHEN (AND ASDF::HOME (NOT (STRING= ASDF::HOME "")))
|      (MERGE-PATHNAMES "site-systems/" (TRUENAME ASDF::HOME))))
|  *DEFAULT-PATHNAME-DEFAULTS* #P"/usr/share/common-lisp/systems/")
`----

here is a ls -l in my ~/.sbcl/systems/:

,----
| lrwxrwxrwx 1 guerry guerry 51 2008-08-02 22:45 cl-ppcre.asd -> 
/home/guerry/.sbcl/site/cl-ppcre-2.0.0/cl-ppcre.asd
| lrwxrwxrwx 1 guerry guerry 59 2008-08-02 22:45 cl-ppcre-unicode.asd -> 
/home/guerry/.sbcl/site/cl-ppcre-2.0.0/cl-ppcre-unicode.asd
| lrwxrwxrwx 1 guerry guerry 55 2008-08-02 22:46 cl-unicode.asd -> 
/home/guerry/.sbcl/site/cl-unicode-0.1.1/cl-unicode.asd
| lrwxrwxrwx 1 guerry guerry 41 2008-08-02 22:50 clx.asd -> 
/home/guerry/.sbcl/site/clx_0.7.3/clx.asd
| lrwxrwxrwx 1 guerry guerry 61 2008-08-02 22:48 flexi-streams.asd -> 
/home/guerry/.sbcl/site/flexi-streams-1.0.5/flexi-streams.asd
| lrwxrwxrwx 1 guerry guerry 80 2008-08-02 22:48 trivial-gray-streams.asd -> 
/home/guerry/.sbcl/site/trivial-gray-streams-2006-09-16/trivial-gray-streams.asd
`----

But this existed *before* I install cl-ppcre system-wide from apt.  
Maybe I should uninstall the local cl-ppcre to avoid conflicts with 
the system-wide one?

-- 
 Bastien