Does not work on Mac

[infinity-computers-dot-net]

I have installed this package into Atom on MacOS, and it shows errors:

• Not connected to SLIME
• Failed to attach to the status bar. Please restart Atom
• Arguments to CompositeDisposable.add must have a .dispose() method

Is this package still in active development?

[neil-lindquist]

I see you were also testing Atom-Slime; have you tried uninstalling that and restarting Atom?
SLIMA is a fork, so having both installed causes issues similar to your second and third bullets.

To start a lisp session, either use the menu option Package > SLIMA > Lisp Process > Start, or search "slime start" in the command palette (ctrl-shift-p).

This package is more in maintenance mode than active development. I do my best to address bugs that come up, but I haven't had much time to develop new features (although pull requests are welcome).

[infinity-computers-dot-net]

Thanks for responding. Starting the session does indeed get me further. However, the lisp code I'm working on doesn't run on the Mac, only on Linux, so I need to debug it remotely.

I tried setting up a swank server on the Linux machine and configuring the plugin to connect to it, but it says it's unreachable...?

Also, when starting a session, *default-pathname-defaults* seems to always be equal to the first project in the Projects panel. How can I change this?

[neil-lindquist]

If you start a swank server on your Mac, can you connect to that?
Also, if you open the dev console (ctrl-shift-i) are there any slima related messages when it fails to connect?

Currently, the first project is always used for the working directory. The only way to change it would be to setup a development version of SLIMA and modify the function I linked (swapping lines 94-95 with 97-98 would use the directory from the current text editor).

[infinity-computers-dot-net]

I figured it out. (swank:create-server) only binds the listening server to localhost. To bind to the LAN address, you need to (setf swank::*loopback-interface* ...) first.

Incidentally, there were no console messages. Bit odd that.

I shall attempt to set up a dev version as suggested. Thanks for the help! :)

[infinity-computers-dot-net]

One more problem with remote debugging: when a breakpoint (or other signal) is hit, the source is not shown because - of course - the file exists in a different place on the remote server. So for example, the file "/user/documents/lisp/myfile.lisp" might be mapped via a network share on the local machine at "/mnt/myserver/documents/lisp/myfile.lisp".

Could you maybe add a configuration option to specify a path to swap out? i.e. something like "replace /user with /mnt/myserver"

Without such an option, remote debugging is pretty much a non-starter :(

[neil-lindquist]

That makes sense given remote code execution is a bit of a security vulnerability. I think another option is to use an ssh tunnel to forward the port.

Yea, there's probably a bunch of places that SLIMA assumes both ends use the same file systems and mountings. I'll have to look at how (if?) SLIME handles it. I haven't tested remote swank servers, so there's probably other, similar assumptions.
But, I've got a number of deadlines coming up, so I probably won't be able to look at it for a week or two.

[neil-lindquist]

I've implemented a basic file-prefix replacement option to the master branch.
I want to test it more thoroughly before I make a new release, but you can try it if you setup a development version of SLIMA.

[neil-lindquist]

I just make a release that includes this prefix-replacement option.
Sorry for the delay.

[Sod-Almighty]

Cheers. I'll give it a try.