<azathoth99>is guile built using epoll? the fast io library? <dsmith-w`>azathoth99: No. But I think I remember wingo doing something with it. ***dsmith-w` is now known as dsmith-work
<ijp>dsmith-work: for future reference, azathoth99 is gavino <azathoth99>for future reference ijp has a 12 inch black strapin <nalaginrut>ArneBab: I'm learning German seriously everyday, dunno how long can I handle it <nalaginrut>maybe I'll post article in German next year, for practice, maybe (next (next year)) <ArneBab>nalaginrut: If you’d like to, I can proofread it for you. <ArneBab>nalaginrut: glad to. Just make sure you highlight me so my computer notifies me ☺ <lloda`>so I want to do (test-assert "test name" (complicated-test A B)), but I want the log to report the values of A & B <lloda`>complicated-test is a form of equal?, I guess <civodul>(test-equal "name" expected-value value) <lloda`>sure, but I want to use my-equal?, not equal? <civodul>i don't think there's anything that would work out of the box <civodul>you'd have to come up with your own macro <civodul>but i see there's 'test-log-to-file', so you should be able to use that <civodul>actually test-log-to-file seems to be a different thing <lloda`>I'll just use test-assert, I think <lloda`>the failures give no info, but heh, tests are supposed to pass :p <ijp>I forgot to report this before, but coverage.tests <ijp>obviously nothing serious, I just wanted to know if it is known/worth fixing <civodul>ijp: ISTR that it's "on purpose", on master <ijp>civodul: odd, you'd think it would be an "expected fail" then <ijp>I'll ask him next time I see him <dsmith-work>sneek: later tell ijp yeah, seemed like a gavino sighting <davexunit>using a different nick. I hadn't heard of gavino. <davexunit>seemed like a beginner that wanted some info <davexunit>I logged off shortly after, don't know if the trolling progressed. <davexunit>paroneayea: things are okay. just dealing with some statusnet/gnu social issues at the moment. <davexunit>spent all morning trying to fix something, still don't have a solution. <davexunit>we did a big upgrade of our CAS server this week that went quite smoothly, except for this... <paroneayea>clearly the answer is to stay at the same software versions forever davexunit <paroneayea>we like our security flaws just how we know and love them. <paroneayea>I knew someone who stayed on the last debian release that had LILO by default for a long time because he didn't want to learn new things, and that was my regular troll to him <paroneayea>he was on debian testing and just didn't upgrade for a long time :) <paroneayea>though maybe in this sense (n|gu)ix can both support slowly migrating systems *and* enable people at the same time :) <davexunit>they can stick with an old version of the repo :P <davexunit>though eventually they'll be forced to compile from source when the build farm GCs old builds. <daviid>civodul, admin quizz: earlier today you said "make sure to equip your Emacs for proper indentation..." I see the version you pointed to is newer then the one in guile source tree and also wanted to ask if I should add a copy of this file to g-wrap, guile-gnome and guile-clutter <civodul>daviid: that's the .dir-locals.el used in Guix, and most of the rules there are Guix-specific <civodul>so i don't think it makes sense to copy it verbatim in other projects ***madsy_ is now known as Madsy