The create-swank-server function in swank-cmucl.lisp has been changed from doing:
(system:add-fd-handler fd :input #'accept-connection)
into just doing:
(accept-connection fd)
This means one must enable multi-processing to run slime. I /think/ the former method is more efficient, but I guess that's marginal. The fact that local set up can more easily break slime is a real downside though. So what's the upside to this change?
I wrote:
The create-swank-server function in swank-cmucl.lisp has been changed from doing:
(system:add-fd-handler fd :input #'accept-connection)
into just doing:
(accept-connection fd)
This means one must enable multi-processing to run slime. I /think/ the former method is more efficient, but I guess that's marginal. The fact that local set up can more easily break slime is a real downside though. So what's the upside to this change?
Follow-up to my own post :-) "must enable" wrong, but the *inferior-lisp* becomes unuseable with the switch, so the question still stands.
"Håkon Alstadheim" haalst@online.no writes:
The create-swank-server function in swank-cmucl.lisp has been changed from doing:
(system:add-fd-handler fd :input #'accept-connection)
into just doing:
(accept-connection fd)
This means one must enable multi-processing to run slime. I /think/ the former method is more efficient, but I guess that's marginal. The fact that local set up can more easily break slime is a real downside though. So what's the upside to this change?
Well, the latter version is simpler and more direct. I reverted the change and the CVS version supports both versions. The fd-handler variant is the default.
Helmut.
-
Helmut Eller -
Håkon Alstadheim