[slime-devel] Re: SLIME+Allegro on Windows
brad.beveridge at gmail.com
Sun Mar 5 18:19:56 UTC 2006
I am by no means a slime, emacs or windows expert - but I have been
looking at slime.el a bit lately. I'm guessing that
slime-start-swank-server may be the reason. It calls
comint-send-string, which I think is an Emacs function to send
something to stdout? Anyhoo, code is
(format "(swank:start-server %S :external-format %s)\n"
That is my suspicion.
On 3/5/06, Peter Seibel <peter at gigamonkeys.com> wrote:
> mikel <mikel at evins.net> writes:
> > 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?
> I was talking to Kevin Layer at Franz about this same issue and I was
> trying to explain why it is that SLIME needs the Lisp to be runnable
> as a console app in order for M-x slime to work and discovered that I
> couldn't. My understanding, such as it is, is that it's because SLIME
> uses the old inferior-lisp mechanism to launch Lisp and that requires
> a console app. But why the need to use inferior-lisp--SLIME
> communicates the port via a temp file, right. Is there some other
> communication that happens via the *inferior-lisp* channel?
> Peter Seibel * peter at gigamonkeys.com
> Gigamonkeys Consulting * http://www.gigamonkeys.com/
> Practical Common Lisp * http://www.gigamonkeys.com/book/
> slime-devel site list
> slime-devel at common-lisp.net
More information about the slime-devel