bug#11293: format and simple-format confused after compiling

2012-04-20 Thread Aleix Conchillo Flaqué
Hi, today I just got a weird issue (probably my fault). I'm trying to write a very basic Guile cookbook for beginners, which is the ony think I know in any case. Anyway, I have this script: #!/usr/bin/guile -s !# (simple-format #t "my first message with a new line~%") (format #t "my first ~a m

bug#13463: web http (fport_write) broken pipe

2013-01-16 Thread Aleix Conchillo Flaqué
Hi I keep my blog using Andy's tekuti and I always update to latest guile. Right now 2.0.7, since last week. This morning I found out that the blog was not running and this is what the terminal showed. Aleix In web/server/http.scm: 158:6 1 (http-write #< socket: # …) In unknown file:

bug#13463: Acknowledgement (web http (fport_write) broken pipe)

2013-01-16 Thread Aleix Conchillo Flaqué
I think you can ignore this by now. It might be a server problem as other services were having problems too. Aleix On Wed, Jan 16, 2013 at 9:30 AM, GNU bug Tracking System wrote: > Thank you for filing a new bug report with debbugs.gnu.org. > > This is an automatically generated reply to let you

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
Hi, I was doing a test using gnutls and connecting to twitter api services. Example attached. I successfully passed the TLS/SSL part, but then I got this HTTP bad header issue. I am running Guile 2.0.5 from Debian/unstable but current stable-2.0 branch also suffers from the safe problem (I think)

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
On Wed, Apr 3, 2013 at 5:34 AM, Ludovic Courtès wrote: > Daniel Hartwig skribis: > >> RFC 2616 _requires_ http date values have a suffix of " GMT" > > What about adding an exception for “UTC”? :-) > > It’s the same timezone, only with a different name, so it shouldn’t cost > us much. > > WDYT? >

bug#14128: web/http.scm: bad-header date check (UTC?)

2013-04-03 Thread Aleix Conchillo Flaqué
On Wed, Apr 3, 2013 at 7:57 AM, Aleix Conchillo Flaqué wrote: > > This is what I did locally so I could continue testing. But > unfortunately, it's is very likely that there are more broken servers > around. The permissive flag seems like an "all-or-nothing", so I thi

bug#38607: unable to build guile 2.9.7 on OS X 10.14.6

2019-12-13 Thread Aleix Conchillo Flaqué
Hi there! Trying to build 2.9.7 on OS X and getting the error below. I'd be happy to try more things if you want. Aleix - wrote `system/vm/elf.go' BOOTSTRAP GUILEC system/vm/frame.go wrote `system/vm/dwarf.go' BOOTSTRAP GUILEC system/vm/linker.go /bin/sh: line 1: 69110 Abort trap: 6

bug#38607: unable to build guile 2.9.7 on OS X 10.14.6

2020-01-12 Thread Aleix Conchillo Flaqué
On Sun, Jan 12, 2020, 12:59 PM Andy Wingo wrote: > On Sat 14 Dec 2019 07:16, Aleix Conchillo Flaqué > writes: > > > BOOTSTRAP GUILEC system/vm/linker.go > > /bin/sh: line 1: 69110 Abort trap: 6 GUILE_AUTO_COMPILE=0 > ../meta/build-env guild compil

bug#54147: [PATCH] doc: fix web (run-server) examples

2022-02-24 Thread Aleix Conchillo Flaqué
* doc/ref/web.texi (Web Server): need quasiquote to in order to evaluate AF_INET6. --- doc/ref/web.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ref/web.texi b/doc/ref/web.texi index 93cd0214f..49a09d0ca 100644 --- a/doc/ref/web.texi +++ b/doc/ref/web.texi @@ -1,

bug#54171: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK

2022-02-26 Thread Aleix Conchillo Flaqué
Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when starting the web server inside containers without the need to having to specify INADDR_ANY all the time. This is the default in most libraries and languages. This doesn't break backwards compatibility since INADDR_LOOPBACK is als

bug#54172: [PATCH] vectors: add (vector-last) support

2022-02-26 Thread Aleix Conchillo Flaqué
* libguile/vectors.c: add (vector-last) support. * libguile/vectors.h: define scm_vector_last and scm_c_vector_last. * doc/ref/api-data.texi (Vector Accessors): add documentation for (vector-last). --- doc/ref/api-data.texi | 10 ++ libguile/vectors.c| 30

bug#60971: GNU Guile 3.0.9rc1 available for testing!

2023-01-23 Thread Aleix Conchillo Flaqué
On Mon, Jan 23, 2023 at 2:48 AM Ludovic Courtès wrote: > Hi, > > Greg Troxel skribis: > > > lloda writes: > > > >> This looks like https://debbugs.gnu.org/60971 < > https://debbugs.gnu.org/60971> on mac os. > > > > Yes, it does. > > > > My quick reaction is that if the POSIX-required macros ope

bug#10490: define-module documentation confusion

2012-01-12 Thread Aleix Conchillo Flaqué
According to the documentation, the module-name in define-module is of the form (hierarchy file). However, one can do (define-module (foo)).

bug#10491: unread-char and eof

2012-01-12 Thread Aleix Conchillo Flaqué
Whenever eof is reach in a port, a call to unread-char passing eof triggers an error. I'm not sure what's the right behavior for this, but I guess the way it is now is just as the user should be responsible to check eof. A note in the documentation would help in any case.

bug#10492: primitive-exit documentation invalid links

2012-01-12 Thread Aleix Conchillo Flaqué
The links for "Normal Termination" and "Termination Internals" are invalid. Should be, respectively: http://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Normal-Termination.html http://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Termination-Internals.html

bug#10491: unread-char and eof

2012-01-16 Thread Aleix Conchillo Flaqué
On Fri, Jan 13, 2012 at 2:34 AM, Daniel Hartwig wrote: > > Suggestions welcome.  Personally I find the documentation sufficiently > clear on the usage of unread-char only accepting a character value and > equally clear that an eof value is not a character. I totally agree. However, I think the do

bug#10491: unread-char and eof

2012-01-17 Thread Aleix Conchillo Flaqué
On Mon, Jan 16, 2012 at 7:31 PM, Daniel Hartwig wrote: > > Nor are type errors mentioned by most other functions, they are simply > implied.  This convention is mentioned in the revised report [1]: > >  It is an error for an operation to be presented with an argument that it >  is not specified to