IRC channel logs

<ArneBab>apteryx: you can write a macro that quotes the object. But this just returns what you already knew at compiletime.

<rlb>Hmm, should "gdb guile" normally work? I ask because I just saw a debian bug report, and I see the same thing. With current debian gdb/guile/libgc, running "gdb guile" and then issuing a "run" causes an immediate segfault in libgc:

<rlb> Program received signal SIGSEGV, Segmentation fault.

<rlb> 0x00007ffff7c10eca in GC_find_limit_with_bound () from /usr/lib/x86_64-linux-gnu/libgc.so.1

<rlb>

<rlb>(current meaning more or less "testing")

<rlb> https://bugs.debian.org/1016630

***daviid` is now known as daviid

***daviid is now known as Guest8421

***daviid` is now known as daviid

<unmatched-paren>Interesting, looks like my configure script accidentally found a bug in dash :P

<unmatched-paren>mksh $ command -v guile >&- -> okay

<unmatched-paren>dash $ command -v guile >&- -> command: command: I/O error

<unmatched-paren>zsh and bash accept it too.

*unmatched-paren going to check if mrsh accepts it

<unmatched-paren>Yes, mrsh works with it too.

<unmatched-paren>Interesting, I guess I really have o

<unmatched-paren>*found a bug in dash.

<alextee[m]>is it possible to use guile on windows without msys?

<unmatched-paren>Hmm. The dash mailing list rejected my email :(

***sneek_ is now known as sneek

<mwette>rlb: I've been running into that on ubuntu. I just continue and all works ok. I did read that the behavior is intentional.

<mwette>It's a gdb thing and not a guile thing.

<mwette>Oh, not gdb, I think the gc.

<mwette>here: https://hboehm.info/gc/debugging.html

<mwette> https://github.com/crystal-lang/crystal/issues/11589

<dsmith-work>UGT Greetings, Guilers

***daviid`` is now known as daviid

<gnucode>wingo_: May I request that you make a blog post detailing the current status of guile-emacs? I appreciate all that you have done for pushing guile forward too!

<unmatched-paren>gnucode: I believe guile-emacs is basically dead. Might be wrong, but all i've heard about it is "it was a GSoC project that's now over and nobody's continuing it"

<dsmith-work>Not quite dead. There has been some work since the GSoC.

<dsmith-work>But it is a single individual, and the Emacs folks are heading in a different direction.

<dsmith-work>sneek: guile-emacs?

<sneek>Last time I checked guile-emacs is http://git.hcoop.net/?p=bpt/emacs.git;a=shortlog;h=refs/heads/wip-bdw-gc

<unmatched-paren>"2015-02-09"

<dsmith-work>Ya, that's pretty old.

<dsmith-work>ISTR some talk here about updates about a year ago.

<ArneBab>unmatched-paren: I see two updates from this year in wip: http://git.hcoop.net/bpt/emacs.git

<dsmith-work>Hey. That's from about a month ago.

<ArneBab>yes :-)

<dsmith-work>So. Not quite dead.

<dsmith-work>A common pattern is furious activty while a person is in school. Then comes a real job, marriage, kids, house, etc. Guile ends up *very* low on the priority list..

<ArneBab>sneek: later tell gnucode: guile-emacs worked, but it was too slow, because it was still missing support for byte-compiled files.

<sneek>Okay.

<ArneBab>dsmith-work: yes, I know that pattern :-) — I’m glad that I am managing to keep working on wisp even though I’m in full-time software engineering employment now (and no longer doing a PhD)

<ArneBab>It looks like guile-emacs doesn’t build right now. See guix shell guile-emacs -- guile-emacs -Q

***Furor is now known as Colere

IRC channel logs

2022-08-11.log