Getting Started - error when running slime

[peterlopen]

tried
docker run --rm -it --user vscode -w /home/vscode ghcr.io/lisp-stat/ls-dev:latest bash
as described in https://lisp-stat.dev/blog/2026/03/09/getting-started/
but got

after pressing 0

pressing 0:

[Symbolics]

Did you run ls-init.sh?

[peterlopen]

No, followed instructions from blog only.

[Symbolics]

Okay,  I’ll leave this open to remind me to update the ‘blog.  The instructions on GitHub should be complete if you need all the details.Basically ls-unit.sh configures the lisp stat system .  You’re seeing that error because the commands in ~/.sbclrc  are trying to initialize a system that doesn’t exist.  Probably ls-unit.sh should add those run commands when you run it so sbcl is always is a runnable state, even without lisp-stat installed.On 10 Mar 2026, at 16:32, peterlopen ***@***.***> wrote:peterlopen left a comment (Lisp-Stat/ls-dev-image#3) No, followed instructions from blog only. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[Symbolics]

OK, the 'blog is now fixed and so is the image. The new image is building now and should be ready within 30 minutes.

[peterlopen]

When copying ls-init.sh from blog, there is only one -, and it seems to take same strange characters. Typing manually it works. However there is some slime error

[peterlopen]

error:
`
[package cl-unicode]..............................
[package cl-unicode-names]..
debugger invoked on a TYPE-ERROR @B800548623 in thread
#<THREAD tid=460 "main thread" RUNNING {1200030003}>:
The value
NIL
is not of type
SB-C::INTERVAL

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry
compiling #<CL-SOURCE-FILE "cl-unicode/base" "util">.
1: [ACCEPT ] Continue, treating
compiling #<CL-SOURCE-FILE "cl-unicode/base" "util">
as having been successful.
2: Retry ASDF operation.
`

[Symbolics]

This is coming from a dependency, not Lisp-Stat itself. What was the sequence of commands to get here? Here's a sequence that should work after you get into the container:

1. ls-init --mode experimenter
2. ls-repl

See if that get's you a configured REPL and then try slime.

[Symbolics]

I have updated and pushed a new image, reworked the 'blog and tested everything.

[peterlopen]

thanks.
unfortunately, still error on running ls-repl
command sequence:

docker run --rm -it --user vscode -w /home/vscode ghcr.io/lisp-stat/ls-dev:latest bash
ls-init.sh --mode experimenter
# ... output from repo checkouts, linking, configuration
ls-repl

error:

[package cl-unicode-names]..
debugger invoked on a TYPE-ERROR @B800548623 in thread
#<THREAD tid=388 "main thread" RUNNING {1200030003}>:
  The value
    NIL
  is not of type
    SB-C::INTERVAL

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

continued with abort, next error:

; Loading "lisp-stat"
..................................................
[package array-operations/generic]................
[package array-operations/reducing]...............
[package array-operations/utilities]..............
[package array-operations/creating]...............
[package array-operations/indexing]...............
[package array-operations/displacing].............
[package array-operations/transforming]...........
[package array-operations/stacking]...............
......
debugger invoked on a TYPE-ERROR @B800548623 in thread
#<THREAD tid=388 "main thread" RUNNING {1200030003}>:
  The value
    NIL
  is not of type
    SB-C::INTERVAL

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):

after abort

; 
; compilation unit aborted
;   caught 2 fatal ERROR conditions

debugger invoked on a PACKAGE-DOES-NOT-EXIST in thread
#<THREAD tid=388 "main thread" RUNNING {1200030003}>:
  The name "LS-USER" does not designate any package.

emacs and slime end in same way:

; Loading "lisp-stat"
...
debugger invoked on a TYPE-ERROR @B800548623 in thread
#<THREAD tid=696 "main thread" RUNNING {1200030003}>:
  The value
    NIL
  is not of type
    SB-C::INTERVAL

[snunez1]

Well, this is strange. You are using the same image and executing the same commands yet are getting different results. Maybe we should step back a bit and examine the environment outside the container.

Have you run a docker pull ghcr.io/lisp-stat/ls-dev:latest between your runs so you get the latest image?

[peterlopen]

no, forgot about it. sorry.
anyway, after pull (and delete + pull) still same error. might be something with m4 hw?

[Symbolics]

Possibly, I'm testing on Intel On Friday, March 13, 2026 at 03:00:32 PM GMT+8, peterlopen ***@***.***> wrote: peterlopen left a comment (Lisp-Stat/ls-dev-image#3) no, forgot about it. sorry. anyway, after pull (and delete + pull) still same error. might be something with m4 hw? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.Message ID: ***@***.***>