IRC channel logs

<lloda>i tried to bisect 75216 but guile wouldn't build or run properly on some of the bisect points and i gave up :-/

<janneke>sneek: tell civodul: just testing sneek

<sneek>civodul:, janneke says: just testing sneek

<janneke>sneek: ty

<janneke>i guess snuik can learn this level of "tell" (next to later tell) pretty easily

<dsmith>I suspect the purpose of the "tell" command (in contrast to "later tell") is when someone has you on /ignore ?

<dsmith>I think what I would like instead is if it would recurse one level

<dsmith>So

<dsmith>sneek, bugs?

<sneek>Someone once said bugs is Send reports to bug-guile@gnu.org, and see bug reports at https://bugs.gnu.org/guile

<dsmith>and "sneek tell janneke bugs? would do soemthing like

<sneek>janneke, Someone once said bugs is Send reports to bug-guile@gnu.org, and see bug reports at https://bugs.gnu.org/guile

<dsmith>I think that would be way more useful

<dsmith>janneke, Hah, just now saw your mail about snuik

<janneke>dsmith: ah, snuik doesn't know about bugs, but you can learn them using something like

<janneke>snuik: bugs is send an email to foo@bar.com

<janneke>dsmith: i guess the tell command is to try to circumvent a filter or block, dunno

<dsmith>janneke, Yes, that's sneek also

<janneke>wondering about it's usefulness too

<janneke>sneek: bugs?

<sneek>Its been said that bugs is Send reports to bug-guile@gnu.org, and see bug reports at https://bugs.gnu.org/guile

<dsmith>I only used "bugs" as an example

<janneke>ACTION heads over to #guix for a bit

<janneke>yeah, i've made snuik is channel-aware for "info/what" and "later tell" because i didn't like sneek to answer a "later tell" in another channel, but yeah dunno

<janneke>dsmith: sure

<dthompson>janneke: very cool that you ported snuik to goblins. :)

<dsmith>janneke, For reference, sneek was a port to guile from sarahbot: https://github.com/igorhvr/bedlam/tree/master/sisc/sisc-contrib/irc/scheme/sarah

<cow_2001>what do i do with unhandled constant errors? https://lists.gnu.org/archive/html/guile-devel/2020-01/msg00161.html says i need eval-when, but nothing really works.

<cow_2001>the problem is bytevector= is defined here before it can be defined but is used in macros https://codeberg.org/kakafarm/guile-bytevector-peg/src/branch/master/bv-peg/codegen/bytevectors.scm#L31

<cow_2001>err mean, it is used in macros before it can be defined

<old>cow_2001: where's the problematic code ?

<cow_2001>it is a bit convoluted and i do not 100% understand the code

<cow_2001>here it is being used https://codeberg.org/kakafarm/guile-bytevector-peg/src/branch/master/bv-peg/codegen.scm

<cow_2001>the record holding this procedure is here https://codeberg.org/kakafarm/guile-bytevector-peg/src/branch/master/bv-peg/codegen.scm#L78

<cow_2001>the procedure is defined here https://codeberg.org/kakafarm/guile-bytevector-peg/src/branch/master/bv-peg/codegen/bytevectors.scm#L31

<cow_2001>trying to use traversable-stuff as a way of packing up the operations on the traversable datatype over which the peg is defined

<old>I don't see bytevector= being used with traversable-stuff?

<cow_2001>it is based on (ice-9 peg)

<cow_2001>it is packed into the bytevector-stuff record, then fed into the (generic-cg-... bytevector-stuff) to create code generators specialised on bytevectors

<cow_2001>the record of type <traversable-stuff>

<old>in make-cg-utf-n for example?

<cow_2001>no, that one is only specific to this module

<old>okay

<cow_2001>i use bytevector= there, but it is not using the bytevector-stuff

<cow_2001>all these generic-cg-... are defined in /bv-peg/codegen.scm

<cow_2001>i think i found it

IRC channel logs

2025-03-12.log