libera/#commonlisp - IRC Chatlog
Search
3:28:11
dieggsy
or, is it possible to run a lisp function defined in the current environment in a separate process
3:30:16
dieggsy
we basically have some legacy build script written in bash and lisp, and i thought "why not just do this in only lisp", but then was like "oh wait because it compiles and loads a bunch of stuff", so I'm trying to... both integrate the code but also separate it from the current environment when it runs ? if that makes any sense at all
4:19:19
dieggsy
ludston: thanks, though that largely concerns launching external programs as a process, and I want to run some lisp as a process
4:19:44
ludston
If for whatever reason you need to sandbox some function in another process, you probably just spin up a new lisp instance with --load "(my lisp code here)"
4:22:14
dieggsy
....i believe process-run-function is spawning a new thread, but i don't completely understand allegro's multiprocessing documentation
4:23:14
ludston
Use bordeaux-threads. It's the defacto standard library that most of us for multithreading
4:24:48
dieggsy
I've used Bordeaux threads in the past, but unfortunately I'm trying to stick with what's built in because of uhhh
4:25:51
dieggsy
though come to think of it i think some parts of the code do use bordeaux threads so maybe i can just sneak that into this bit as well
4:28:45
ludston
I work on a really horrible, old code-base (not lisp) too. In my experience it is better not to get stuck in the "not invented here" mindset and use the library/make the sweeping change that you are afraid to make.
4:30:28
ludston
The worst thing that can happen is your experienced code-reviewer says no and then you learn why.
4:31:39
dieggsy
well, the worst that could happen is "why" is just "that's not how we do it" and well ok you're the boss heh
4:38:55
dieggsy
fe[nl]ix: STScI, only like a month in. (employer if you are reading this i am sincerely having a blast) jajaja
6:09:36
hexology
what would cause the error `Component :CL-BASE64 not found, required by #<SYSTEM "hunchentoot">` when running `(asdf:load-system "hunchentoot")` under qlot+roswell?
6:12:24
hexology
and the qlfile has `ql hunchentoot 2021-04-11` and `ql chunga 2021-04-11` (wasn't sure about the right dates to use)
6:15:19
hexology
am i misusing qlot? it looks like it's not installing dependencies when i run `qlot install`
6:27:03
hexology
i must be doing something wrong that's very simple, i have read all the qlot and roswell docs several times
10:45:13
selwyn
for me, it is C:/Users/selwyn/quicklisp/local-projects/ on a fresh quicklisp install
10:47:13
selwyn
though for actual development i use the portacle quicklisp installation which is itself under the msys2 home directory
10:57:59
tfb
shka: my point was, you don't need to: write a program which uses that variable. If you need, say, to run programs in some other language to install things there, spawn them from CL
11:11:13
selwyn
if you are deploying it is not wise to rely on or expect the existence of quicklisp though
12:07:57
ludston
In your lisp init file, (e.g. .sblrc) it will specify the directory that quicklisp is installed in. By default this is (user-home-pathname) which on Windows uses the "HOME" environment variable.
12:09:03
ludston
I'm not sure what (user-home-pathname) is by default because mine is set to my msys64 home dir
12:13:55
ludston
If you are using lisp on Windows, I'd highly recommend using something like msys, because a lot of libraries rely on open source dll's. You can set your "Path" environment variable to point to C:\msys64\mingw64\bin and then install external dependencies with pacman
12:15:32
selwyn
when i start sbcl under msys64, it does indeed instead install quicklisp under the msys64 homedir
12:16:18
selwyn
it´s best to just stick to doing everything under msys, and you also get a shell to use
12:17:06
ludston
If you open up "Edit the system environment variables" you can set the HOME directory so that it is always msys, even if you launch sbcl outside of msys
12:20:55
Duuqnd
I'm probably not doing that myself though because my Windows computer is already messed up with like three different msys/mingw things installed somehow
12:21:41
splittist
My problem (on Windows) is not lisp and its idea of home (/Users/me), it's emacs and it's weird idea (:
12:22:16
tyson2
I'm just getting started with sbcl on windows, and have it working with slime, etc. But I've decided to set up a local docker sbcl instance and use that instead.
12:24:29
tyson2
that way I can avoid all the drawbacks of adding linux-workalike libraries for sbcl on windows which I have already encountered
12:26:09
tyson2
seems to be good support for docker in emacs, docker-tramp etc., will test it out this weekend
12:27:12
ludston
Deployment on windows is only easier when everybody copies the same .dll into every separate install
12:28:46
tyson2
eventually I will skip the local container and just develop directly on the docker sbcl instance on the vps
12:30:37
tyson2
on AWS lightsail, you can now deploy docker instances directly, without first installing linux