8:46:41dimlast time I tried to profile pgloader the profiler worked but didn't get useful information, because in a typical small-data run we start a lot of short-lived threads
18:06:30cage_i have two systems with conflicting nicknames, how can load (via ASDF) both in the same system?
18:07:23cage_my best "solution" (so to say) is to define a system that just remove the offending nickname from one of the system that needs to be loaded
18:09:52phoecage_: when there's PLNs, there will not be much use for short nicknames since library writers will be able to define their own per-package nicknames
18:10:55cage_ i see, so far is just CCL that does not have this feature?
20:19:59ThomasLewis[m]Yeah, I was just reading that. It is supposed to inherit the environment by default and use execvp to find the executable. Try providing the full path in the `program` string. If that doesn’t work, try #P”/path/to/uname”
20:27:23Xachsb-ext:run-program's cmucl kitchen-sink functionality roots make me happy
20:30:15dimmmm, I now see :wait nil :status-hook ... and I wonder how much I'm missing
20:31:15dimI should really learn how to avoid “Heap exhausted during garbage collection” when using SBCL, then I guess I would be quite happy with that implementation
20:35:45dimexpect libs and things, or just mutli-threaded control of background jobs, sounds quite powerful
20:36:08Xachdim: i had a program that did (with-current-directory "foo" (run-program "bar")) but with threads it broke, and using (run-program "bar" :directory "foo") fixed it.
20:36:24dimanyway, I can't depend too much on SBCL until I know how to make its GC happy, and I obviously am very far from that at the moment
20:36:27XachI think run-program's guts do the chdir after the fork and before the exec.
20:36:38Xachhaven't checked, just been a happy user