IRC channel logs

2019-09-10.log

back to list of logs

<rlb>Is there a typical way to launch a subprocess allowing capture stderr in addition to stdout?
<weinholt>rlb, it's a bit cumbersome but can be done, here's an example: https://github.com/rotty/spells/blob/master/spells/process/compat.guile.sls
<amz3>hello all!
<amz3>spk121: is webkit gtk already in a useable state? I need to crawl websites rendered using javascript. The "algorithm" is the following 1) go to url http://example.com 2) render the page 3) store the html of the page inside a .html file
<amz3>sometime it is called browser automation
<rlb>weinholt: ahh, I see -- was hoping to avoid primitive-fork given the potential threading issues, but I'll take a closer look later. Thanks.
<csed>Hoi hoi, so on the website I saw: "In addition to Scheme, Guile includes compiler front-ends for ECMAScript and Emacs Lisp"
<csed>What's the elisp bit mean? Does it compile to elisp byte code?
<ft>No, it can compile elisp source code to the guile vm.
<ft>So it would generally be possible to swap out emacs' elisp engine with guile. But it might be doubtful whether or not that will happen.
<rekado>this already happened (see Guile Emacs), but work on it has stalled.
<ft>Sure, I meant whether or not the default engine in emacs gets replace by guile.
<spk121>amz3: I'm not sure how much of WebKit is usable now. It works well enough to make small example work. https://github.com/spk121/guile-gi/blob/master/examples/browser.scm
<spk121>amz3: everything common is working except for struct accessors, GHashes, and some closure operations
<spk121>and the autogenerated documentation isn't great
<csed>ft, rekado: Ah, righto. Thanks!
<dsmith-work>Morning Greetings, Guilers
<spk121>dsmith-work: heya
*spk121 ponders bizarre plan to have a GNU-only website using GNU Serveez as http server, GNU Artanis as web framework, and GNU recutils as database backend
<civodul>:-)
<rotty>With glibc on the HURD, of course, spk121! ;-)
<rotty>Does guix run on the Hurd? Throwing guix into the mix would round the thing off nicely, IMNSSSO.
<rekado>rotty: it’s complicated, unfortunately.
<rekado>we’re having some problems with the cross-built bootstrap binaries on the Hurd.
<rotty>(IMNSSO = In my not so serious opinion) ;-)
<ArneBab>rotty: since the Hurd has been self-hosting its wiki for something like a decade now, that’s not as far-fetched as it sounds.
<rotty>ArneBab: my last hurd experience was in the early 2000's when I had a dual-boot with linux for a while
<rotty>I was really sad that the l4-based rewrite never seemed to pick up steam
<ArneBab>rotty: it didn’t pick up speed, because they found l4 to lack a bit too much. Once they focussed on Mach again, progress was slow but steady.
<rotty>ArneBab: do you happen to have any links regarding that? I'd love to read up on that decision, and the limitations of L4 discovered.
<ArneBab> http://darnassus.sceen.net/~hurd-web/history/port_to_another_microkernel/
<ArneBab>you can try the Hurd again today: wget http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.tar.gz; tar xf de*hu*gz; qemu-system-x86_64 -hda de*hu*g -m 1G # user is root
<ArneBab>You might get more answers in #hurd
<rotty>ArneBab: thanks