IRC channel logs
2025-07-14.log
back to list of logs
<daviid>Kolev: what was this isp fix about? a #scheme user says they can't visit the link either <Kolev>daviid, I had to disable Spectrum Security Shield in the My Spectrum app. <graywolf>I just though I would let you know. :) Additionally, your version seems to lack some quoting, "$(dirname "$(realpath "$0")")" this will allow it to work in directories with spaces <ArneBab>sneek: later tell graywolf: thank you! I switched back to to #!/usr/bin/env bash, because that’s portable over to almost every system (/bin/sh could be dash) and added quoting for d=, but otherwise I switched to your version. <lechner>Hi, what's a better way to read a uint64 on x86_64 than (pointer-address (dereference-pointer ...)) please? <wingo>(pointer->bytevector p 8 0 uint64) <wingo>(pointer->bytevector p 8 0 'u64) <dodoyada>anybody have suggestions on emacs settings/packages relevent to guile font locking? I use a lot of sxhtml->html and would like to indicate function invocation over symbols in situations like `,(a-function '(div ...` <dsmith>dodoyada, No clue. But might I suggest asking in #emacs (if you havn't already)? <dodoyada>I asked #scheme but not #emacs, will try there <lechner>wingo / thank for that hint, but it throws off processing of the ELF auxiliary vector <lechner>wingo / now it worked! a (bytevector-u64-native-ref bv 0) brought it over the line <lechner>Hi, why might a valid C pointer (the original argv in a patched Guile) cause a segmentation fault when packaged with scm_c_define ("%original-argv", scm_from_pointer ((void *) argv, NULL)) and later printed via 'display'? <rlb>wingo: fwiw, I think I may try your bytestring-flavored bytevectors suggestion, and I suppose I'll make them contagious (wrt append, etc.) and see how that looks, if it's not too hard. Guess we could also keep the print-enable to allow setting the default for other bytevectors. <lechner>Hi, how may I keep the load path across a (set-current-module (make-fresh-user-module)) please?