freenode/#lisp - IRC Chatlog
Search
23:33:53
jasom
Any 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:13
jasom
also if someone has a script for setting up a slime-over-ssh tunnel easily that would save me some time
0:16:39
cgay
Somehow never saw this before. Fun read. https://www.cs.umd.edu/~nau/cmsc421/norvig-lisp-style.pdf
5:29:37
drmeister
::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.
6:14:59
phoe
before 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:28
phoe
this way I avoid problems with translating names from local to remote ones, because they are the same.
10:55:28
myrkraverk
This is related to linedit; I already have a fork of it under my own (github) name; but I want to pull in changes from another fork
11:00:40
myrkraverk
Ok, so I need to first checkout my copy, *then* pull in changes from the other repository? And what happens if I want to make a pull request for the "other repository" ?