***KDr2 is now known as KDr21
***KDr21 is now known as KDr22
***KDr22 is now known as KDr23
***KDr23 is now known as KDr24
***Server sets mode: +nt
***apteryx_ is now known as apteryx
<janneke>rekado_: eli could have had a kinder response...but he does voice a frustration that i also feel: too little cooperation within gnu <janneke>it's probably a matter of timing, attention etc., but feeling discouraged or frustrated is something that can happen fast <killmeplease>I've noticed a lambda (like the letter lambda, unicode and shit) in some guile things I've been looking at <killmeplease>Is that a quirky variable name which the interpreter allows or do I have to learn some keybindings? <lloda>you don't have to use it and I don't <killmeplease>variable name or syntatic sugar for the word lambda or something BTW? <spk121>killmeplease: the greek lambda lambda is a syntax rule in core guile that maps directly to the world lambda ***wxie1 is now known as wxie
<spk121>janneke: Did you ever find a way to make Guile debugging meet your needs? <janneke>spk121: no...my patch also had a puzzle (and probable bug) about breakpoints <janneke>spk121: i wanted to raise/address those issues /after/ guile backtraces would be GNU/GUD-friendly <janneke>i did not spend any more efforts there, it was probably not the right time <spk121>janneke: I've tried a few times to make Guile's breakpoints work in a way that makes sense to me, but, without much success. Mostly now, I use my fancy logging library when I develop in scheme. <janneke>spk121: it was pretty hard to introduce guile in my workplace and have people "go back to the 70s printf debugging" as one co-worker framed it <janneke>one day, we'll gave Guile Studio (TM) with wonderful guile debugger integration <janneke>at the time, i was not ready to look deep enough into guile internals, i'm slowly warming up to the idea <mwette>Hi folks. I looked into adding "-g" flag to compile.scm and using that to flag the cps utilities to not reuse registers. If you hit a breakpoint ,locals whould show everything, hopefully. I had to put it down for a bit, though. <janneke>mwette: very nice; that would be super helpful <dsmith-work>I used edebug for the first time ever yesterday. Pretty cool. <spk121>dsmith-work: is edebug a guile thing or an emacs thing? <dsmith-work>emacs thing. But it is lispy. Didn't know what to expect. <killmeplease>spk121: ah so syntatic sugar. Thanks. I'd lost the tab with the code in it you see, otherwise I'd have posted it. <jcowan>What are people here's views of the Guile Studio effort? It's intended to be a newbie-friendly skin of GUI Emacs. I've been reading about it on the ML <dsmith-work>jcowan: I saw that message. Nothing there for me I think. I already have long years of emacs experience. Don't want something that makes it "user/newbie friendly". <dsmith-work>I'm all for better Guile support. But not for dumbing-down emacs. <jcowan>killmeplease was complaining that Emacs was too alien for him to learn, and I wonder if GS would help. <dsmith-work>Eclipse is the tool of choice for embedded vendors to make a gui. <dsmith-work>And I *always* have a hard time with it. I can never figure out how to do what I want. <dsmith-work>t "help" me by writing/OVERwriting my makefiles for me. Ugh. *dsmith-work takes a timeout to make some tea <jcowan>"The IDE is emacs. The build tool is make." --Not Sepp Herberger <dsmith-work>One nice thing about emacs, is the interface has been pretty much constant over decades and whatever fad-of-the-day OS you are using. <jcowan>"Constant", that is, if you take your .emacsrc around with you. <OrangeShark>hmm, for Guile Studio, it would be a similar idea to Lispbox? <OrangeShark>oh the other one that I am aware of is called portacle which combines emacs + sbcl + quicklisp + git in a package <oni-on-ion>cannot find anything about guile-studio, and having searched before. so to me it is vapourware <oni-on-ion>but i do not know how to access it, or what it is all about. <oni-on-ion>guile picture language i've installed, its great =)