Is there a way to keep the source files on the local client, if the lisp image is on a server?
I know of -tramp files are on the server :-( -rsync same problem. -ssfs from the server to the client: Pro: the client needs no driver installation Cons: the server needs some.
How to you resolve that problem?
Helmut
Is this what you are looking for?
http://common-lisp.net/project/slime/doc/html/Connecting-to-a-remote-lisp.ht...
-austin
On Wed Aug 29 14:00 , helmut@cybernetic-systems.de wrote:
Is there a way to keep the source files on the local client, if the lisp image is on a server?
I know of -tramp files are on the server :-( -rsync same problem. -ssfs from the server to the client: Pro: the client needs no driver installation Cons: the server needs some.
How to you resolve that problem?
Helmut
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Honorable Austin Haas writes on 29.08.2007 15:37:
Is this what you are looking for?
http://common-lisp.net/project/slime/doc/html/Connecting-to-a-remote-lisp.ht...
No, that ist TRAMP - Mode. The files are on the server, slime translates the pathnames for emacs (main.lisp -> remote.server.com:/tmp/main.lisp) and emacs uses tramp to access the server files. ... and then you have to sync (update) your local files!
I'm looking for an method where the swank part fetches the source file via emacs. Emacs can already send a buffer content to the server like a listen input. So the way "C-c C-k" request a file from emacs-slime shouldn't that far.
Helmut
-austin
On Wed Aug 29 14:00 , helmut@cybernetic-systems.de wrote:
Is there a way to keep the source files on the local client, if the lisp image is on a server?
I know of -tramp files are on the server :-( -rsync same problem. -ssfs from the server to the client: Pro: the client needs no driver installation Cons: the server needs some.
How to you resolve that problem?
Helmut
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel