IRC channel logs


back to list of logs

***aleogen_ is now known as aleogen
<kristofer>how might I combine two lists of records together? I don't need them sorted
<rain1>(append l1 l2)
<kristofer>rain1: perfect, thanks
<amz3>,héllo :)
<dsmith-work>Morning Greetings, Guilers
<wleslie>greetings dsmith!
<paroneayea>hello #guile!
<paroneayea>davexunit: do you have haunt crash sometimes while you're running "haunt serve"?
<paroneayea>I get segfaults sometimes
<paroneayea>I think it's from guile-reader.
<davexunit>paroneayea: no I've never seen that
<paroneayea>davexunit: I've had it happen about 5 times now while working on 8sync's site.
<paroneayea>davexunit: I saw something, I forget what, which indicated it might have been guile-reader related.
<davexunit>I've never seen a segfault. there's a bug in 'haunt serve --watch' but this seems unrelated to that
<paroneayea>davexunit: ok, next time I see it, I'll see if it spits out more info
<davexunit>paroneayea: okay, thanks!
<davexunit>segfault is bad bad bad :(
<paroneayea>davexunit: I've only seen it during "haunt serve", and it seems fairly random.
<paroneayea>I wish I knew how to reproduce it!
<davexunit>are you using --watch? I don't see why 'haunt serve' would do anything with guile-reader otherwise
<paroneayea>davexunit: yes I'm using --watch
<paroneayea>and changing a lot of things as I go
<paroneayea>davexunit: it's possible that I've saved files which are incomplete
<paroneayea>davexunit: and maybe that broke things.
<davexunit>I need to patch --watch to not crash the thread if the site compilation throws an error
<davexunit>but it should definitely not segfault1
<paroneayea>I save a lot as I hack.
<paroneayea>heh :)
<davexunit>I need some sort of ignore/print-exceptions form
<paroneayea>I need to get out an 8sync release. I guess I'm planning on rearchitecting things to use poll (and maybe epoll) but
<paroneayea>I should probalby just release what I have as 0.0.1
<paroneayea>needs more docs too, but sitting on this code without a release is frustrating
<davexunit>I know that feeling
<davexunit>I need to apply your haunt patch, patch 'haunt serve --watch' and release 0.2
<davexunit>I felt really unmotivated to work on code this weekend so I didn't get anything done.
<davexunit>I can only really focus on this hardware hacking project of mine but I'm hitting roadblocks with that, too.
<kristofer>amz3: I found your graph module on the mailing list! is there an example of how to use it?
<rain1>suggestion: rename this from q to queue
<mthl>rain1: I think your suggestion make sense.
<mthl>rain1: would you like to do the work? if so please send your suggestion to guile-devel
<davexunit>it's a public interface, and thus it can't really be renamed.
<davexunit>or rather, such a rename would have to be saved for a backwards incompatible release of guile
<janneke>it seems that guile's configure checks for the existence of iconv.h, but won't work without it
<rain1>sent a patch
<wingo>davexunit: heya
<wingo>are you a chunked-encoding person
<wingo>ah no that it ijp
<wingo>ACTION sets all soft ports on fire
<davexunit>yeah not me, sorry.
<davexunit>ACTION saw the twitter
<davexunit>I weep for you
<wingo>it's all good
<wingo>ok, i have all the port read and write functions operating on scheme data structure
<wingo>it's like every port is really an r6rs binary port
<wingo>kinda cool
<davexunit>that's really cool
<wingo>the r6rs custom port interface maps precisely to guile's internals
<davexunit>that's some good luck
<wingo>makes me happy about r6rs ;)
<wingo>oh hey it's an eye jay peep
<wingo>ijp: do you use http chunked ports for output?
<wingo>i saw you wrote that code a while ago and i was just in it
<wingo>would there be any issue you'd expect if we flushed the ports by default every N characters?
<wingo>N since the last force-output i mean
<ijp>I think I only ever used it for reading
<ijp>no issue I can think of
<ijp>ACTION looks
<koz_>wingo: Is guile-lib still an active thing? The Guile site says that it's 2.0-compatible, but guile-lib's documentation says that it's only good for 1.8.
<ijp>it should still work, but I don't think anyone is adding to it
<koz_>ijp: So it's moribund then?
<ijp>I guess? What are you needing it for?
<wingo>guile-lib works with 2.0 fine
<paroneayea>still in progress
<paroneayea>but hey, it's up and viewable!
<davexunit>paroneayea: I think it's great!
<paroneayea>davexunit: no css frameworks! all css3 stuff :)
<wingo>paroneayea: pretty fly!
<paroneayea>thanks davexunit, wingo
<paroneayea>hopefully release shortly
<davexunit>heh, and I should release haunt 0.2 and guile-syntax-highlight 0.1
<paroneayea>davexunit: yes / yay
<paroneayea>I'm using both, so :)
<rain1>would you like feedback on the example ?
<davexunit>I'm glad that the syntax highlighter worked for someone besides me. the second user of a piece of software is an important one. ;)
<paroneayea>rain1: sure (though it's imaginary, so that's one piece of feedback ;))
<rain1>I read the comment but I still don't understand it
<rain1>so maybe a simpler example would help?
<paroneayea>rain1: yeah that comment could maybe be confused. I hope to have additional information below it.
<paroneayea>rain1: hm I'm not sure a simpler example exists...
<rain1>but the design of the site looks lovely and the code is really big which is great!
<paroneayea>er, that comment could maybe be made less confusing
<paroneayea>gotta go
<paroneayea>thx rain1 !
<koz_>ijp: Just curious, 'tis all, since I saw a disjoint between what the Guile website said and the docs.