IRC channel logs


back to list of logs

***daviid` is now known as daviid
<apteryx>rekado_: here's my goal:
<apteryx>I don't really know what I'm doing but this seems to work:
<apteryx>which kind of makes sense: don't do anything in fdown or fup (except reverse at last), but accumulate each node.
<apteryx>can I traverse a tree while expanding it? seems not. what algorithm/technique would be more suited for that?
***Bocaneri is now known as Guest5006
***rumgzy is now known as Sauvin
<manumanumanu>So... how many times per year does someone enter the channel and ask for the recently added open-at?
<manumanumanu>Does Maxime ever come here?
<lilyp>I don't imagine it to be many since those behind openat also work on Guix, it's primary "customer" ;)
<manumanumanu>oh :( It'll save other people some headache anyway
<manumanumanu>So, I have a compiled guile. How do I run it without having to do a make install?
<civodul>manumanumanu: you can run ./meta/guile from the build tree
<sneek>civodul, you have 3 messages!
<sneek>civodul, podiki[m] says: looks like a bug in fhs container after as the glibc-for-fhs package may not appear if another package propagates (I think) glibc
<sneek>civodul, podiki[m] says: I think because of glibc-for-fhs being added to the ad-hoc packages before/after what the user specifies? not sure, will see if I can come up with a fix but can confirm glibc (regular guix) can appear instead of the fhs version
<sneek>civodul, podiki[m] says: throwing in a reverse for options/resolve-packages in (guix scripts environment) would fix it... so maybe just make sure glibc-for-fhs appears last?
<manumanumanu>I make about one patch every 2 years, so I always forget
<manumanumanu>I am getting a lot of truncated-print errors when compiling from main...
<manumanumanu>and I get a load of errors regarding =>
<manumanumanu>"failed to autoload truncated-print in (ice-9 pretty-print) ... ... unknown location: => bad use of '=>' syntactic keyword in subform => of =>"
<manumanumanu>but => is defined in boot-9.scm, so that shouldn't be an issue...
***fanta1 is now known as fanta1|away
***fanta1|away is now known as fanta1
<manumanumanu>oh no. I have done something stupid.
<lilyp>manumanumanu: => is defined to a syntax error ;)
<lilyp>you probably messed up your macro somewhere
<lilyp>dthompson: do you think it might make sense to release a guile-sdl2 0.7.1 in time for ALGJ 2022?
<dthompson>lilyp: yes, that's on my todo list!
<dthompson>lilyp: do you have any other patches you want to get in before I do that?
<lilyp>I don't think so – I was more "concerned" about the Guix packaging side, since one patch that is already slated for release makes packaging Tsukundere easier
<dthompson>lilyp: I can probably get the release out tomorrow.
<lilyp>nice, I'll maybe also do a bugfix release for Tsukundere
<dadinn>hi all
<dadinn>I am trying to configure lsp-mode for scheme/guile using lsp-scheme. It doesn't seem to be able to start up. Has anyone managed to use this?
<mwette>apteryx: for the tree-folds: Not sure what you mean by traverse while expanding but fdown may be for what you mean. example:
<sneek>mwette, you have 1 message!
<sneek>mwette, cwebber says: oh wow thank you!
<vbramselaar>Hi all, I'm trying to distribute my guile script pre-compiled. When I put everything in the right system load-paths, only the starting script is still auto-compiled?
<vbramselaar>Like I have a guile script with a main, that uses some of my modules
<vbramselaar>all is compiled
<vbramselaar>but only that script with main needs recompilation, how come?
<vbramselaar>And does --no-auto-compile mean that already compiled files, if they are present, are not used? Or still used?
<unmatched-paren>vbramselaar: i believe --no-auto-compile means that files won't be pre-compiled and cached if they aren't already compiled
<vbramselaar>but if pre-compiled files are already present in /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache, they are still used?
<vbramselaar>Or is there a way I can check?
<unmatched-paren>i think so
<unmatched-paren>i'm not sure
***rgherdt_ is now known as rgherdt
<manumanumanu>lilyp: I know... I am re-defining cond in boot-9.scm to expand to (let () ...) instead of begin to add support for internal definitions in cond clauses, but for some reason it results in compilation errors. I have only made the patches on a running system, and then it works fine...
<manumanumanu>which is... odd
<manumanumanu>there is something psyntax that I am missing here...
<lilyp>note that psyntax needs to be precompiled
<stis>hello guilers!
<stis>hello prologeurs!
<manumanumanu>lilyp: now it works, so it seems I was doing something wonky the first time. :)