When I used to work on Windows I always just launched ACL in a window and used slime-connect from emacs or xemacs. It's not as pretty as launching via M-x slime but I always work that way so I can restart emacs or my lisp separately (I have many long-running jobs). That's the quick & dirty answer to working on Windows.
Ian
mikel wrote:
Franz wants Peter Seibel's Lispbox to work with acl on Windows. The obstacle is that acl is not a console application on Windows, and doesn't provide a connection to standard input and standard output in the normal way. I've agreed to do a little legwork to find a way around this problem, and the first thing it occurred to me to do was to ask SLIME-devel what sort of connection support SLIME would need to connect to acl. Is it sufficient for the running acl to provide sockets, so that the lisp-side server can respond to the emacs-side SLIME protocol?
What issues am I not thinking of in my naive view of this problem?
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel