*paroneayea installs drracket, out of curiosity ***sethalves is now known as sethAway
***sethAway is now known as seth
***seth is now known as sethalves
<mark_weaver>please_help: could you use 'array-contents' to create a flattened 1 <nalaginrut>each time reply to " please_help ", it looks just like the answerer is requiring help... <wleslie>there is this one cat with the nick 'lubyou' <wleslie>I don't really like repyling to them (: <lloda`>please_help: why aren't you using array-index-map! here? <lloda`>also I have a patch up in git that will replace the whole top begin block in your code by (apply array-amend! ret result idx) <lloda`>but first you should replace all this manual indexing by array-index-map! <wleslie>it's really cool when my worlds collide (you having a conversation with cfbolz on twitter) <zacts>mark_weaver: hey do you use org-mode literate programming to code? <zacts>or do you just code directly? <paroneayea>would it be useful to have a topsort function in standard guile? <paroneayea>and I found I couldn't open slib with guile in debian <paroneayea>maybe might be nice to just include it in guile's standard library, was easy to port over <taylanub>paroneayea: you'll probably get more attention on guile-devel, but the developers might be busy and not react unless you provide a complete patch <taylanub>paroneayea: ;; is when the comment is the only thing on a line, but after indentation, ; is at the right side (margin) of a line of code <taylanub>and ;;; is when the comment starts at zero indentation <taylanub>paroneayea: Emacs's M-; command does the right thing :) <mark_weaver>daviid: the problem is that the bug is happening not in the code you're running, but in the REPL/compiler itself. <mark_weaver>typing ,backtrace at the top REPL wouldn't work anyway, because you are not in the debugger. <mark_weaver>most likely the error happened while trying to print one of your data structures that has a custom printer. <daviid>mark_weaver: tx, by the way, before answering the above, I got rid of all reported errors while compiling kisê against guile-2.1 [and so it is compiled and i don't think it is a kisê bug here, but a guile-gnome using guile-2.1 problem/bug, let's see]. after these changes, kisê still runs perfectly using 2.0 [and guile-gnome built against 2.0] <daviid>the previous paste was an attempt to get a full bactrace from an emacs session where i manually load ... but here is a terminal output http://paste.lisp.org/+34IL/2 as you can see, kisê s already compiled... how can i get a fullbacktrace of this ? *davexunit is missing a lot of mail from guile-user