I am attempting to get started on some guile hacks. I am running Emacs, Geiser,
Guile (2.0.11) for Scheme development.
I have cloned the git repository for Guile (current commit d545e45). I can
configure
and build this tree. I can run the executable
$ GUILE_TREE/libguile/guile --version
guile (G
First of all, congratulations with the 2.1.3 release! :-)
I just finished setting up a continuous integration server at
http://guile.mechcore.net:8080/
It periodically polls the origin/stable-2.0 branch every 12 hours,
builds 32-bit freestanding versions of guile for Windows, and packs it
up
Hi,
On Tue 21 Jun 2016 22:36, Ricardo Wurmus writes:
> This is the same patch I sent to the discussion of bug#20339 about a
> year ago.
Yeah sorry for the miscommunication; two lists, split brain.
> The patch is not very ambitious: it only gives the user a way around the
> error by letting the
Andy Wingo writes:
> On Mon 20 Jun 2016 12:52, Ricardo Wurmus writes:
>
>> Andy Wingo writes:
>>
>>> Apologies for the long delay here. I'm with you regarding namespaces
>>> and sxml->xml. In the past I made sure to always get the namespaces
>>> attached to the root element via the @ xmlns a
On Tue 21 Jun 2016 14:38, Zefram writes:
> Andy Wingo wrote:
>>Thoughts?
>
> How was this managed in Guile 1.8?
The printers and the backtrace handling was quite different, but it used
"print states".
> It seems that you need the truncated-print mechanism to be always
> available internally, bu
Andy Wingo wrote:
>Thoughts?
How was this managed in Guile 1.8?
It seems that you need the truncated-print mechanism to be always
available internally, but this doesn't require that it be always visible
to the user. You can still require the full libraries to be loaded for
the user to get access
Not really sure what to do here.
Ideally we could just use ~@y in the format messages. However we can't
rely on having a full format loaded up, only simple-format. We could
lazily load the full format when needed, but I don't know if we should
train users that the full `format' is always around.
Hi :)
I dunno how much we should push this "processes are a single port"
abstraction. In many ways for OPEN_BOTH pipes it's easier to deal with
an input and an output port and a PID instead of the pipe abstraction.
WDYT? We could just expose `open-process' from (ice-9 popen) to start
with. It w
Andy Wingo writes:
> Please fix the commit log. Thanks :)
Whoops, here we go:
>From 232757c7f99d39beb16a09cd81a94670f6249ba2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
Date: Fri, 2 Oct 2015 22:56:04 +0200
Subject: [PATCH 1/2] Fix SRFI-2 (and-let*) i
On Tue 21 Jun 2016 00:38, taylanbayi...@gmail.com (Taylan Ulrich
"Bayırlı/Kammer") writes:
> From 8405987e86cd99772f81f98565e66f673e82d57e Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
>
> Date: Fri, 2 Oct 2015 22:56:04 +0200
> Subject: [PATCH 1/2] Fix
10 matches
Mail list logo
