IRC channel logs

2026-03-11.log

back to list of logs

<czan>Quick one: if I want to do the equivalent of "touch -m" (i.e. update mtime) in Guile, what's the best way to go? I was hoping (close-port (open-file filename "a")) would do it, but it doesn't. Alternatively, (call-with-output-file file (const #t)), which Guix uses, deletes the file contents.
<rlb>czan: perhaps (utime ...)
<czan>Sheesh, that's concerningly easy. I really should have found that, given it's documented very clearly. Thanks!
<rlb>Certainly. Guile has pretty good POSIX-ish coverage.
<czan>Clearly I rely too much on the info index, and assuming I know the right words. :P
<dariqq>suddenly i have lots of incompatible guile bytecode warnings in my guix checkout, was there a change recently?
<identity>dariqq: there definitely were changes related to Guile in Guix
<dariqq>hmm guix uses guile-3.0-latest which is now guile 3.0.11, but all the guix guile support libraries are built against guile 3.0.9 , this should definitly create problems, no ?
<cbaines>is anyone able to look at https://codeberg.org/guile/guile/pulls/95 ?
<ekaitz>dariqq: make clean-go && make
<dariqq>oh sry i just noticed i wrtote this in guile and not guix
<ekaitz>dariqq: some of us are in both channels, even the bot is the same!
<avigatori>Hello!
<avigatori>Should I report "bugs" in the documentation on codeberg too? It's strickly a documentation thing. A chapter is missing/has no content
<avigatori>sorry, section, not chapter
<ekaitz>avigatori: yes
<ekaitz>please
<avigatori>ekaitz: is the guile/guile repo the correct one for this manual? https://www.gnu.org/software/guile/manual/html_node/index.html
<ekaitz>i'd say so, es
<ekaitz>yes
<avigatori>thank you :)
<ekaitz>no problem
<ekaitz>you could even make a pr with the contents of the docs, just sayin'
<avigatori>I looked into that but I couldn't find it ._. Admittedly I didn't look for too long
<rlb>If it helps, all the docs are generated from doc/ref/*.texi.
<rlb>(all the reference manual)