freenode/#lisp - IRC Chatlog
Search
20:55:12
rpg
Xach: Thanks. Seems like this will hamper use of CL for tasks that involve data analysis...
20:56:02
Xach
rpg: sure. if someone needs that to do data analysis and they want to use lisp, they will have to make it.
20:58:11
Xach
rpg: sometimes when i want something like that i fake it with run-program, e.g. (with-open-ssh-file (stream "user@host:path/blah") ...) it would just run scp and copy it to a local file, rather than try to do much fully in lisp.
21:00:29
phoe
so just call the proper sshfs commands in some sorta directory and then use logical pathname translations to refer to that temporary directory
21:02:09
Xach
I think logical pathnames are for when you have an enumerable set of literal pathnames embedded in the code, not for arbitrary translations with runtime variations
21:03:27
White_Flame
IMO, this is something the OS really should handle. The fact that all networking is bound to just a plain host:port is a massive weakness
21:04:20
Xach
I think it's a bummer that people start with the idea of arbitrary, configurable runtime pathname transformation and get Very Upset when logical pathnames don't do that, but I don't think that's fully the fault of logical pathnames
21:06:32
rpg
phoe: sshfs sounds neat. I'm with Xach though about logical pathnames -- I think there's too much danger that the filenames would break the LP rules, turning that into a mess.
21:35:25
rpg
Xach: I bet that's possible with ABCL, now that I think of it, but I'm not a JVM kind of guy.
21:47:03
rpg
phoe: Yes. Looks like someone set up an sftp file stream for python, but it's an add-on
21:49:47
jasom
rpg: just curious; I had a few documentation ideas and wasn't sure who to run them by once they are more complete
21:50:17
rpg
Please send them my way! I just got an idea for a new FAQ that I will try to put into the manual today.
21:52:23
jasom
okay. Will do. I'm going to go back through the mailing list and some reddit posts because things that have been obvious to me for years w.r.t. asdf seem to still be hangups for others.
21:54:07
jasom
The number of times I've seen some variation of "I wish I could just load an ASD file and then have my system be loadable" come up is rather stunning since the manual is pretty clear on not just "yes that will work but "We even hook into slime's C-c C-k so that you don't need to do anything special if you're using slime"
21:56:55
jasom
life is finally slowing down enough for me that I can possibly contribute to projects in places I've noticed I might be of assistence
22:21:54
rpg
jasom: I have to take off momentarily, but feel free to contact me if you need assistance -- TeXinfo isn't the easiest thing to edit! (but FWIW, it's a lot better than Python's Sphinx...)
1:43:45
jasom
Let's say I want to define a new component type for asdf. Once I have done so, I can use it with :components ((foo:bar ...) *but* now a :defsystem-depends-on is insufficient to pull in my customization becaue the whole form is read before the defsystem-depends-on is processed. What's the solution?
2:03:31
jasom
One solution is to put a defpackage at the top of the .asd file; I'm looking at iolib.asd now
2:10:43
jasom
It's only non-composable in the sense that it imposes a single global namespace. Package names have the exact same problem.
2:11:31
jasom
in terms of name collisions there's not really any difference between :foo-bar and foo::bar, but packages provided other forms of isolation that are useful.