On Fri, 24 Jun 2005 09:02:15 -0700, peter@gigamonkeys.com wrote:

Peter Seibel peter@gigamonkeys.com writes:

So it's not just me. The common variable may be Windows XP--does anyone have SLIME running successfully on Windows XP? With CLISP?

SLIME works fine with Personal Lispworks and 21.3 GNU emacs. But I use AutoIt, thus hiding whatever details are needed here. --------------------

Run, "C:\Program Files\Xanalys\LispWorks Personal\lispworks-personal-4300.exe" WinWaitActive, Upgrade LispWorks LeftClick, 330, 410 Sleep, 1000 WinActivate, Listener 1

Send, (load "slime"){ENTER} Sleep, 2000

WinMinimize, LispWorks Personal Edition 4.3.7

Run, "C:\Program Files\emacs\bin\runemacs.exe" WinWaitActive, emacs@TICKER Sleep, 1000 send, {ESC}xslime-connect{ENTER}{ENTER}{ENTER}

Exit ------------------------------ "slime" ------------------------------ (load "c:/Program\ Files/emacs/site-lisp/slime/swank-loader.lisp") #-clisp (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t) #+clisp (swank::create-swank-server 4005)

--------------------

I don't remember if I have the Hyperspec working and it has been awhile since I used this lisp setup, but it never had a problem I as I recall.

So it's not just me. The common variable may be Windows XP--does anyone have SLIME running successfully on Windows XP? With CLISP?

Windows-xp + slime cvs +clisp cvs is working on my pc with a minor patch to nregex.lisp (defun regex-compile (source &key (anchored nil)) ... (t ;; ;; This is a subgroup repeated so I must build ;; the loop using several values. ;; needed for broken clisp cvs head t )) ...

I also had to allow the socket server to the firewall.

salud2

Karsten

On Sun, 26 Jun 2005 14:57:46 -0700, peter@gigamonkeys.com wrote:

dice. If I manually call (swank:start-server "c:\slime.port") and then M-x slime-connect it all works. So I don't think it's a firewall

Then a working solution would be the autoit macro I posted eariler, modified appropriately. You can attach the macro to a desktop icon, which makes it pretty easy for lisp visitor.

So I was able to get this working with CLISP 2.33.1. The firewall was a non-issue. The first time I fired it up, it basically worked. Windows popped up a dialog informing me of the TCP connection and basically asking what I wanted to do. I enabled it for Emacs/CLISP and things worked well.

The problem, where ever it lies, is something that changed between CLISP 2.33.1 and 2.33.2. From what I can tell, something is failing and preventing the server socket from getting created. I inserted debug routines into all the various create-server sort of routines in SWANK and they aren't getting called when Swank first starts. The only thing I can surmise is that some CLISP routine called earlier is returning an error that Swank doesn't like and it's just bailing out. The death is quiet. No messages and no Lisp debugger loop. It basically just loads everything and never gets around to starting the server.

To be honest, I have no idea what changed between 2.33.1 and 2.33.2. I was just using 2.33.2, I think like you, because it was the latest available tarball on the CLISP web site.

BTW, whatever the problem is here is specific to CLISP. The same issue occurs whether using SLIME 1.0 or 1.2.1 tarballs.

-- Dave

On Sun, 2005-06-26 at 20:10 -0700, Peter Seibel wrote:

So, as I mentioned in another message, I have the Windows firewall completely turned off. Dorking around with slime.el it seems that the problem is that in slime-start-swank-server the call to

(comint-send-string process (format "(swank:start-server %S :external-format %s)\n" file encoding))

is having no effect. In fact, it doesn't seem to be happening at all. I put something in the elisp that loads slime to trace comint-send-string and I put a call to message right before the call to comint-send-string and I see the message but no sign of any activity from comint-send-string. However if, in the *inferior-lisp* buffer I call swank:start-server with the same arguments as it was supposed to be called with here, a) SLIME then finishes conecting and starts up and b) I see the trace of comint-send-string. So does anyone have any idea why this isn't working? FWIW, I have cygwin installed on this box but I'm not (as far as I know) using it in Lispbox--I have a .bat file that launches Lispbox and I'm using the plain vanilla binary distributions of Emacs and CLISP.

-Peter

"Karsten Poeck" Karsten.poeck@gmail.com writes:

"Peter Seibel" peter@gigamonkeys.com wrote in message news:m2br5sebpr.fsf@gigamonkeys.com...

...

starts up and b) I see the trace of comint-send-string. So does anyone have any idea why this isn't working? FWIW, I have cygwin installed on this box but I'm not (as far as I know) using it in Lispbox--I have a .bat file that launches Lispbox and I'm using the plain vanilla binary distributions of Emacs and CLISP.

Is the clisp binary you are using based on mingw or on visual c?

Dunno; it's whatever the clisp-2.33.2-win32.zip available from Sourceforge is.

I will try to create a mingw build, but I don't have the compiler to create a visual c version. My working version is based on cygwin.

So you built 2.33.2 yourself under cygwin? I assume that such a binary will only run on machines that have cygwin installed, right? Is there any chance you could download the win32 binary from Sourceforge and let me know if that works for you?

-Peter

"Karsten Poeck" Karsten.poeck@gmail.com writes:

...

So you built 2.33.2 yourself under cygwin? I assume that such a binary will only run on machines that have cygwin installed, right? Is there any chance you could download the win32 binary from Sourceforge and let me know if that works for you?

Ok, done that and also tried a mingw build. Summary: clisp cvs head cygwin works with slime cvs head clisp cvs head mingw (no need for cygwin) works with slime cvs head clisp released version for windows from sourceforge does not work (starts up, loads slime but does not connect)

Okay, so now that my subject line is further justified, I'd be delighted if anyond has any brainstorms about what's going on with the 2.33.2 CLISP for Windows available from sourceforge. I'll be digging into it more myself of course and will post whatever I discover but if anyone has any ideas, please send them my way.

-Peter