Current connection influences slime-init-command via slime-tramp

[Anton Kovalenko]

slime-tramp module provides slime-filename-translations variable: instead of writing a complicated translation function, we're able to build an alist mapping (machine-instance) values to other functions.

There is a problem, however, when some CL implementation is running and another one is started: (slime-init-command) calls filename translation function, and it uses (machine-instance) from the old connection. So the names of e.g. swank-loader and "port file" are translated _according to the slime-tramp mapping for some old connection_.

Seen this problem on slime-tin20110320-cvs (version in quicklisp).

Implementing new-target-specific translation for (slime-init-command) seems impossible, if I understand correctly: slime has no reliable way to know (machine-instance) when it prepares command-line arguments for CL executable. At least I'd prefer this initial translation to be unaffected by old unrelated connections.

[Stas Boukarev (stassats)]

I recentely removed translations from slime-init-comand compeletely, because I don't see how it ever can work properly. And it's usually used on a local connections anyway.