23:33:53jasomAny hints for a fully-remote slime debug; I can connect to slime remotely and use tramp for opening the remote files, but do I need to do anything to get them all to play nicely together?
23:34:13jasomalso if someone has a script for setting up a slime-over-ssh tunnel easily that would save me some time
23:39:47Josh_2can't you remote connect with emacs?
23:40:01scymtymjasom: the slime-tramp contrib seems to be intended for that use case
0:16:39cgaySomehow never saw this before. Fun read. https://www.cs.umd.edu/~nau/cmsc421/norvig-lisp-style.pdf
5:29:37drmeister::notify shiho Pull the latest clasp 'dev' and start building it again. I had introduced a problem in the previous version that only showed up when building quicklisp. The new 'dev' fixes it.
5:29:37Colleendrmeister: Got it. I'll let shiho know as soon as possible.
6:13:40phoejasom: I actually do a thing to wok around tramp hacks.
6:14:59phoebefore I connect to the slime, I mount my Lisp projects directory using sshfs on the same location, so /home/phoe/Projects/Lisp/ refers to the same directory with the same contents both on the remote machine and the local one.
6:15:28phoethis way I avoid problems with translating names from local to remote ones, because they are the same.
6:39:47cess11_drmeister: Awesome, thanks for sharing.