IRC channel logs
2024-10-14.log
back to list of logs
<ekaitz>arg, it's too late, i'll try again tomorrow <wizard>newbie question but how do people manage the load path when it comes to multi-file programs? <wizard>is it common to put (add-to-load-path ".") in ~/.guile? <wizard>does everyone work in a guix shell all the time maybe? <wizard>every solution i see seems to become very sensitive to changes in the cwd, which isn't bad but i'm just wondering if that's how everyone's working <ekaitz>i'm still trying to upstream my first changes <ekaitz>janneke: if i'm not mistaken you didn't touch the PEG syntax that much, right? <ekaitz>looks like my changes are pretty compatible with these <ekaitz>ludo told me to test my changes against some things we have in guix <ekaitz>those are really interesting, i'll add those too <ArneBab>wizard: I use shell-indirection an dput into my script exec guile -L "$(dirname $0))" -e '(the modulename)' -c '' <wehlutyk>oops, I think I'm figuring out my mistake -- ignore all this for now! <old>On guile-next in a REPL, (environ) prints a warning because of unsafe usage of it in multi-thread process <old>which is something I introduced. However, I don't get the warning with primitive-fork. Even though both use the same check <old>Odd that in a REPL, there are two threads <old>this is really weird. Sometime I have one thread, sometime two when executing a guile script <old>this seems arbitrary. I delete some syntax rule and I now only have one thread