IRC channel logs

<zacts>has lilypond been ported to guile-2.0 yet?

<zacts>hi frofroggy

<frofroggy>The guile manual can be reflective at times.

<zacts>how do you mean? :-)

<frofroggy>"But perhaps this reflects the cognitive limitations of the programmer who made the current interface more than anything else."

<zacts>heh

<frofroggy>it's rather humble

<zacts>lo

<calher>How did this pan out? --

<calher>"We had a person working last summer finishing up a

<calher>translator from Python to Scheme." --RMS

<mthl>--RMS (in 2002)

<mthl>:)

<mthl>I guess you have your answer

<ArneBab>calher: it’s no translator, but a way to get a similar feel to the code: http://draketo.de/english/wisp

<calher>ArneBab: Wisp is cool, but I like Lisp.

<janneke>ArneBab: found and read your page, googling for python+guile

<ArneBab>janneke: nice!

<janneke>ArneBab: just an hour ago, great read!

<ArneBab>calher: it is a lisp ☺ (I like parens for some parts of the code, for other parts I prefer pure indentation)

<ArneBab>janneke: I’m glad to hear that ☺

<ArneBab>if you want more info why I prefer Guile to Python, now, you can get the py2guile PDF: http://draketo.de/proj/py2guile/py2guile.pdf

<janneke>or actually, i found http://draketo.de/proj/py2guile/

<janneke>yeah, that's what i read

<janneke>i could have written that title, very recognisable sentiments for me!

<ArneBab>☺

<ArneBab>janneke: feel free to share it with anyone who might care — the book is licensed under GPL, too.

<janneke>that's great, i will

<calher>ArneBab: I know, you can write Scheme/Common Lisp/Emacs Lisp with Wisp, but I don't like it. I like all the parens.

<calher>ArneBab: Whoa, 107 pages...

<calher>ArneBab: People complain that I look at code with a lot of Lispisms.

<calher>ArneBab: Where's the source to that PDF?

<ArneBab>calher: at https://bitbucket.org/ArneBab/wisp

<ArneBab>calher: sorry, here: https://bitbucket.org/ArneBab/py2guile/

<peterbrett>Hello everybody!

<peterbrett>Does anyone know what might be causing this error in my Windows build?

<peterbrett>While executing meta-command:

<peterbrett>ERROR: In procedure bytecode->objcode: bad bytevector size (4942 != 4880)

<peterbrett>This is while doing ",u (geda os)" (loading part of the gEDA core library)

<peterbrett>I'm guessing wingo might have a clue, as compiler-botherer-in-chief

<peterbrett>This is guile 2.0.11

<peterbrett>I can stick a zip file of Windows binaries somewhere if it would help

<calher>Windows 10?

<peterbrett>calher: Yes, Windows 10

<calher>peterbrett: This computer has a copy of Windows 10, but I don't know how to troubleshoot and I'm too lazy to reboot into Windows.

<peterbrett>calher: Um, thank you

<ArneBab>peterbrett: maybe madsy can help

<ArneBab>(when he’s around)

<madsy>peterbrett: Not an error I've seen before. Then again, I have only tested 2.0.11 on Windows 7 and Windows 8.1

<peterbrett>madsy: :-) Thanks though

<madsy>Did you build guile as 64-bit by any chance?

<peterbrett>No, it's not possible to build Guile 2.0.11 for Windows x64

<madsy>Right, just checking

<peterbrett>numbers.c errors out :D

<peterbrett>So -- something weird is going on, and I'm not sure what

<peterbrett>Do you have any suggestions about how I might go about debugging this?

<madsy>I'm not sure. Maybe using gdb via MSYS could work

<madsy>peterbrett: Another check: Did you use the exact same version of guile for strapping the Windows build?

<peterbrett>Yes, I was building Guile 2.0.11 with Guile 2.0.11

<madsy>With the same features enabled/disabled too?

<peterbrett>Hmm

<peterbrett>That's a good question

<peterbrett>Possibly not

<madsy>The build guile compiles code for the host guile, so they have to be exactly compatible.

<peterbrett>Okay, I'll look into it :) Thank you :)

<madsy>Other people here might have a better clue as to how "equal" they have to be

<peterbrett>my configuration is --enable-static=yes --enable-shared=no --disable-rpath --enable-debug-malloc --enable-guile-debug --disable-deprecated --with-sysroot=<path> --without-threads

<madsy>If everything else fails, you culd try my build script

<peterbrett>So I'm sure something in there could screw things up

<madsy>Looks like the settings I use too

<peterbrett>Yes, they are :D

<vanila>hi

<vanila>do you use guile inside emacs or a seperate terminal outside?

<vanila>what is best?

<rekado>vanila: I like to use Geiser in Emacs.

<vanila>Geiser ok thansk ill try it out

<vanila>darn I got a bug when trying geiser :(

<vanila> https://github.com/jaor/geiser/issues/105

<vanila>the 0.8 release didn't work, latest from github works

<calher>rekado: http://b.1339.cf/hnvzimf.txt

<davexunit>something about asset processing failed

<davexunit>I think?

<davexunit>maybe try removing the static asset config for now and see if it will work otherwise

<vanila>it seems hard to use geiser

<vanila>when you do C-c C-k compile buffer it puts you into a debug window then you have to do extra work to get into the repl

<davexunit>that's not normal

<vanila>yeah i cant get it to cooperate nicely

<calher>rekado: Ah! I still can't get haunt to build!

<calher>rekado: Is there a *really* simple page that I could try?

<davexunit>calher: the git repo has an example site

<davexunit>that should build just fine if your setup is correct

<calher>davexunit: But it doesn't work, and it refs an image for crying out loud!

<davexunit>calher: I can't tell what you're doing wrong, but you're doing something wrong.

<davexunit>building the example site from git master will require you to use a version of haunt built from git master

<calher>it work snow

<ArneBab>nice!

IRC channel logs

2016-01-17.log