About problem with slime connection unexpected closed when a bluetooth serial connection is broken.
Nikodemus Siivola nikodemus@random-state.net writes:
2009/6/1 Helmut Eller heller@common-lisp.net:
Perhaps it helps if you install a signal handler for SIGHUP to ignore it. It might also help to bind process-connection-type in slime-start-lisp to 'pty instead of nil.
If SIGHUP is the cause, then
(sb-unix::ignore-interrupt sb-unix::sighup)
is the immediate bandaid to making SBCL ignore it. (Caveat: SB-UNIX is an internal implementation package, and the APIs there may change or go away without warning -- if this solves your problem, let us know so that when someone has enough spare cycles we can figure out a supported API for your needs.)
The (sb-unix::ignore-interrupt sb-unix::sighup) works, so the SIGHUP theory seems very plausible. I haven't tried to bind process-connection-type to 'pty yet.
I will try that tomorrow.
Thanks a lot for figuring this out, it makes it much more pleasant to work on this. (The NXT device shut itself off after a period of inactivity, and it was very annoying that the lisp image was killed as well.)
Kind regards, Wim Oudshoorn.