***M-TimePath is now known as TimePath`
<wingo>srfi-19 string->date doesn't allow you to leave off the year; irritating <rain1>Is there a library for xorg/X11 with guile? <rain1>I've been wanting to use it buit waiting for a new release <rain1>is there a way I could make the new release happen? <rain1>Although I would need some guidance <rain1>oh okay, I thought it was just changing a variable in a config file and then pushing that out/packaging and stuff <mark_weaver>if it was easy, it would have been done years ago :) <linas>saying guile | tee does not work as expected... <rain1>is there any info about the guile gobject introspection version of gtk project? <mark_weaver>although there are gobject-introspection bindings for guile, as I recall. <mark_weaver>but this job requires someone who's knowledgeable about gobject-introspection and how it can be used to create language bindings semi-automatically. <rain1>Are there any easy for beginners guile things to contribute towrds? <mark_weaver>rain1: btw, I'm not saying that writing guile-gnome-3 is necessarily out of your reach. but if you want to do that, you need to do your homework yourself :) <mark_weaver>I can answer questions, but I don't have time to walk you through the process <mark_weaver>but the basic idea would be to use gobject-introspection and Guile's dynamic FFI to automatically create wrappers for all of the Gtk/Gnome APIs. <rain1>that's definitely a very cool idea <amz3`>there is already a scheme library doing that for various scheme implementation <amz3`>I don't recall the name right now <mark_weaver>that's what we'd like to move towards, and if we had that, it would be easy to update to new APIs as they come along, because gobject-introspection is meant to provide the necessary information to automatically create wrappers. <rain1>maybe I'll play around with gobject-introspection a bit <janneke>ACTION very much enjoys morning greetings at 18:09 <cojy>when i try changing (ice-9 control) i start getting ;;; WARNING: .../control.scm failed ;;; ERROR: no code for module (ice-9 control) <cojy>anyone know what im doing wrong and how to do it right? <cojy>even if i revert the changes it does it <mark_weaver>cojy: sounds like you'd introduced an error in that file, so it can't be compiled successfully. <cojy>like i said even if i revert the changes, so that can't really be it ***alexei___ is now known as amgarchIn9
<linas>mark_weaver well, I said this (with guile-2.1 from git): guile |tee foo then (+ 2 2) but 4 is not printed until I ccontrol-D to quit <mark_weaver>linas: ah, I checked guile-2.0, not guile-2.1. last I tried, guile-2.1 doesn't compile on i686, which is what I'm stuck on at the moment, so I can't try it. <mark_weaver>but my first guess is that maybe the output port is configured for full buffering. you might try changing it to line-bufferred, or unbuffered. <mark_weaver>yeah, at the moment, x86_64 is the only architecture that guile-2.1 seems to build successfully on. it fails on i686, armhf, and mips64el anyway <mark_weaver>at some point, we'll have to make it more portable :) <mark_weaver>I haven't yet found the energy to read and comprehend the intmap code <amz3>rain1: did you find the scheme library that does GI? <amz3>I had a look libuv header, this aweful much more complicated to bind that wiredtiger <amz3>aweful lot is maybe a lot of talking <amz3>anyway, it requires bytestructure, that's what was holding me from starting to bind it <daviid>amz3, rain1, sbank is missing bits to work with guile, so said rotty last time I could chat with him here <paroneayea>In between other things, I am *attempting* to rewrite bipt's elisp commits in changelog format ***M-TimePath is now known as TimePath`
<daviid>is there a way to search in our channel logs? <rain1>it seems like the site itself doesn't let you <daviid>wingo: did you patch master for (define (qux str k) (let lp ((kk (string-length str))) (and (>= kk k) (lp (1- kk)))) (qux "foo" 0) -> unnamed port>:1:60: Value out of range 0 to 18446744073709551615: -1 <daviid>dsmith-work: our bot is on holiday? :) <paroneayea>lfam: in a changelog style commit, if I have a whole bunch of functions like this <paroneayea>but baz not only moves, but also does something else <lfam>I'm not sure. When I need to answer questions like that I usually try to find a prior example in the logs. If I couldn't find an example, I'd probably use the former method. That assumes it makes sense to move them all together, which it probably does if it's all in one commit. That way the reader doesn't have to hunt to figure out what moved; it's all in one place. <paroneayea>lfam: okay, well good enough for me, since that was my instinct as well. <paroneayea>Since I'm waiting for an environment to rebuild, I'm doing the changelog adjustments for the elisp branch ;P <paroneayea>some of these commits are huge. I'm not *totally* sure what's going on, but I'm doing a best guess and leaving in the description <paroneayea>(Best-ability ChangeLog annotation added by Christopher Allan Webber.) <paroneayea>that way it's clear that the ChangeLog stuff *could* be wrong but is the best I could do. <lfam>You are resurrecting an old branch? For Guile or Guix? <lfam>That yak is always very hairy <paroneayea>lfam: I'm rebasing bipt's elisp support for guile <paroneayea>but it lacked changelog style commits for some branches <holomorph>fwiw what lfam said was my approach for making commits to emacs, and no one has pinged me for anything aside from capitalizing or ending with a period <lfam>I'm no authority on this subject ;) I just do my best to copy the examples in commit log