On Sat, 2 Oct 2004, Helmut Eller wrote:
Andras Simon andras@renyi.hu writes:
Looks like there's something wrong with multiple connections anyway. slime-goto-connection and ,restart-inferior-lisp don't seem to work.
Works for me :)
Hm, I wonder what I'm doing wrong. I tried it with acl/cmucl, and hitting RET in the *SLIME connections* buffer just put me in the REPL of the default connection.
One problem I see with this (and I may very well be wrong about it) is that in that case slime-process must not only be set at startup, but kept up-to-date. E.g. if a lisp dies, the corresponding slime-process should be set to nil.
slime-process looks at the process-status and returns nil if the process is dead.
Yes, that's what it does now. But you wrote:
| I see; that's a problem. Perhaps we should make slime-process a per | connection variable and initialize it at startup, i.e. when SLIME is | started with M-x slime.
and it's this suggestion (that slime-process be turned into a per connection variable) that I reacted to.
Also, is there any way to set it at startup other then by calling inferior-lisp-proc, say, in slime-start-lisp?
No, we have no special way. But inferior-lisp-proc should be good enough for the initialization.
OK.
Andras