Recently, I've been running a Lisp-based server on a batch scheduling system.<br>
The scheduler starts up my server on an available machine and then I'd like to<br>
connect to it with Slime.&nbsp; I've noticed two things:<br>
<br>
1.&nbsp; The code in swank.lisp listens on port <a href="http://127.0.0.1">127.0.0.1</a>, which means I cannot<br>
connect to my Lisp server from a remote machine.&nbsp; I must log in to the host<br>
it's running on and then specify &quot;localhost&quot; when I execute slime-connect in<br>
Emacs.&nbsp; If swank is running on host &quot;foo&quot;, why doesn't it bind its listening<br>
socket with foo's address?<br>
<br>
2.&nbsp; I modified swank.lisp so the server code binds its listening connection<br>
socket with foo's address.&nbsp; Now I can connect from a remote machine.&nbsp; Is there<br>
any convenient way to send whole files across the Slime connection?&nbsp; The<br>
Lisp running the swank server has no NFS access to the machine I'm running<br>
Emacs on.&nbsp; I'd like to be able to edit files on the Emacs side and send then<br>
whole to the Lisp running swank.<br>
<br>
bob<br>
<br>