Getting the lisp process that serves our webapp to run persistently they way I want it to has been trickier than expected. Why am I even surprised by things like this anymore?
I've tried using both screen and detachtty, but since the errors I'm getting seem to be independent of either, I'd say I prefer detachtty for my purposes, since it's less featureful and therefore simpler to use. Here's what I can't do: start a sbcl with detachtty, create a swank server, connect to it from emacs with M-x slime-connect, and have it actually work. Here's what I was doing since that didn't work: opening emacs, doing M-x slime, and just not closing the window. Here's what I'm doing now that I think is slightly better: starting sbcl with detachtty, not starting a swank server and trying to connect to it from emacs, and just running the app from the repl. I'm guessing that the error Weblocks was giving me when I tried to run the app after doing slime-connect isn't related to the warning I got when starting the swank server (The class SB-PRETTY:PRETTY-STREAM was not changed, and there's no guarantee that the loaded code (which expected another layout) will work. [Condition of type SIMPLE-ERROR]), but I wonder. I'm also guessing the app error is unrelated to the error I would SOMETIMES get when trying to do slime-connect (error in process filter: Elisp destructure-case failed: (:invalid-rpc 5 "Thread not found: :REPL-THREAD")), but that one seems a bit worrisome. I found this page: http://www.dunsmor.com/lisp/slime-w-long-running-processes.html to be very helpful as far as using detachtty, but it took me a while to figure out why it didn't work exactly for me. The post is a bit old, and so it doesn't account for the fact that instead of (swank:create-swank-server 4005), I needed to just type (swank:create-server).↧
