freenode/#clasp - IRC Chatlog
Search
18:14:01
Shinmera
I had a hacky patch that fixed it, but it did it in a way that wasn't entirely right and broke with some libraries so I had to remove it again
18:15:09
drmeister
I'm building everything relative to /opt/clasp - I tried to get clever and build it in a local directory and symlink /opt/clasp to it - but asdf was having none of it.
18:17:51
Shinmera
Here's an email chain that I sent to ASDF devel once https://mailman.common-lisp.net/pipermail/asdf-devel/2017-December/005993.html
18:28:12
drmeister
My solution is easier than yours - I'm going to build at /opt/clasp and install at /opt/clasp
18:28:34
drmeister
I was trying to be fancy and build at wherever/opt/clasp and then install at /opt/clasp
18:31:59
drmeister
Bike: We still have the source-debug-pathname option for compile-file. IIUC Fare was suggesting in the email chain that an option to compile-file that substituted an arbitrary logical pathname for source info would be a good solution to Shinmera's problem.
18:32:40
Bike
i think the function descriptions have a T_sp for the pathname, so i guess that's fine
18:33:21
drmeister
I don't think so - but it might be a good idea to implement Fare's idea as a generalization. I'm a bit confused as to what source-debug-pathname does these days - do you recall?
18:36:30
drmeister
Right - so a better names for the source-debug-xxx arguments might be source-tracking-pathname and source-tracking-offset and then allow source-tracking-pathname to use logical pathnames?
18:37:34
drmeister
The idea is that the output of a C-c C-c compile-file operation is a small fasl that with source tracking info that points to the original file and offset in the original file - correct?
18:39:54
drmeister
If it permitted logical pathnames then we have the clasp implementation details for what Fare is proposing here https://mailman.common-lisp.net/pipermail/asdf-devel/2017-December/005996.html (less the changes to ASDF).
0:59:20
drmeister
stassats: Is there a way to tell slime to move its cache directory from ~/.slime to elsewhere? The manual doesn't say.
1:02:35
drmeister
Those are two different approaches - right? As in (1) "Open C-x C-f slime.el and figure it out from there" or (2) "ln -s wherever ~/.slime"
1:03:29
drmeister
Ah - I see this... https://github.com/slime/slime/blob/master/swank-loader.lisp#L154