[Bese-devel] sbcl / swank

[Keith Irwin]

Folks--

I *finally* got UCW examples up and running.  If you're thinking about
tutorials, just some basic config stuff would be nice.  For instance,
using mod_lisp2, you have to set an Alias in http.conf in order to get
the stylesheet to serve up.

A basic quick how-to for starting/stopping the server would be nice,
too (though I got hints from init.lisp).

Maybe it's way too early in your development cycle before that kind of
thing is necessary.  I notice there's no bese-users list. ;)

ANYWAY, I'm really excited about exploring this framework!

So, the one problem I have is trying to connect to the running server via slime.

 * emacs from cvs
 * latest slime (cvs -q update)
 * sbcl 0.8.20 (on ubuntu: i.e., threads)
 * ucw 0.3.7

To reproduce:

----
gnome-terminal
sbcl
 * (load "init.lisp")
<watch spewage>

start up a new emacs
M-x slime-connect <ret> 127.0.0.1 <ret> 4005
----

Slime then seems to just hang there.  However, if I go to the terminal
and hit C-c, effectively shuttdown something (the socket connection is
there, I think, but nothing gets served), slime then will connect.

* If, in emacs/slime, I do a (ucw:shutdown-server ...), I'm fine.

* If I then do: (ucw:startup-server ...), the server starts, but the
repl is blocked.

* If I instead go to the terminal and (ucw:startup-server), the
emacs/slime repl is blocked as well.

Is this expected behavior?  (I tried starting a new swank listener
from the admin console, no go either.)

Just to test, I opened a terminal, started sbcl, (require 'swank),
(create-swank-server), then opened a fresh new emacs, M-x
slime-connect yadda yadda and it worked, so I'm guessing it's not at
least an obvious config issue outside of UCW itself.

SO, maybe this is a bug?  Perhaps it's an FAQ?

Any help appreciated!

Again, looking forward to seeing how this style of webapp development
can bring back some of the fun.... ;)

Keith