Hi David,
> I mean, Guile doesn't *need* to include anything, but JSON is one of
> the most common serialization formats around. Most language
> implementations ship with a JSON library. Guile already has a suite
> of web modules and so this fits right in with those. Over the years
> I've noti
Hi David,
Thanks for the patch. I'm just trying to understand: Why do we need a
JSON module in guile itself? Isn't guile-json, the way it is as an
external library, good enough?
> API that can read/write JSON to/from a port using only Scheme data
> types that have read syntax (i.e. no hash tabl
* .mumi/config: New file.
* .gitignore: Add .mumi/current-issue.
---
.gitignore | 1 +
.mumi/config | 3 +++
2 files changed, 4 insertions(+)
create mode 100644 .mumi/config
diff --git a/.gitignore b/.gitignore
index 0dbca7366..5ea0179ba 100644
--- a/.gitignore
+++ b/.gitignore
@@ -152,3 +152,
repository. This will
allow us to use the mumi CLI client as documented in the Guix manual at
https://guix.gnu.org/manual/devel/en/html_node/Debbugs-User-Interfaces.html#index-mumi-command_002dline-interface
Thanks!
Arun Isaac (1):
Add mumi config.
.gitignore | 1 +
.mumi/config | 3 +++
2 files
Hi Guile,
Both (split-and-decode-uri-path "foo/bar") and
(split-and-decode-uri-path "foo/bar/") return '("foo" "bar"). The
trailing slash is lost. The trailing slash traditionally represents a
directory path, and is significant. I would expect
(split-and-decode-uri-path "foo/bar") to return '("f
Rob Browning writes:
> Arun Isaac writes:
>
>> A few minor typo fixes and documentation improvements follow.
>>
>> Arun Isaac (3):
>> doc: Fix return value of do loop example.
>> texinfo: Fix typo in transform-string docstring.
>> doc: Improve d
That's great, thanks!
> As the author of most of the part with corrections: thank you. I am
> cleaning up the reference implementation as well, so this is very
> welcome!
You're welcome! :-) I find SRFI-171 to be very useful. It has changed
the way I write scheme code.
signature.asc
Description: PGP signature
* doc/ref/api-foreign.texi, doc/ref/srfi-modules.texi: Fix typos.
---
doc/ref/api-foreign.texi | 2 +-
doc/ref/srfi-modules.texi | 32
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/doc/ref/api-foreign.texi b/doc/ref/api-foreign.texi
index 2bd46
Hi,
The libraries page at https://www.gnu.org/software/guile/libraries/
displays "guile-email" wrongly as "guile-email.systemreboot.net". This
is because lines 76-82 of
https://git.savannah.gnu.org/cgit/guile/guile-web.git/tree/website/apps/base/libraries-page.scm#n76
make certain problematic ass
* doc/ref/api-control.texi (while do): Change return value of second do
loop example from 789 to 243.
---
doc/ref/api-control.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index 5df5344c5..9860457fa 100644
--- a/doc/ref
* doc/ref/api-data.texi (Shared Arrays): Replace "either" with "either
array" in make-shared-array documentation.
---
doc/ref/api-data.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index ed14b2298..012c114e5 100644
--- a/
* module/texinfo/string-utils.scm (transform-string): Replace "te" with
"the" in docstring.
---
module/texinfo/string-utils.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/module/texinfo/string-utils.scm b/module/texinfo/string-utils.scm
index 42074d334..8c81c20fc 10064
A few minor typo fixes and documentation improvements follow.
Arun Isaac (3):
doc: Fix return value of do loop example.
texinfo: Fix typo in transform-string docstring.
doc: Improve documentation of make-shared-array.
doc/ref/api-control.texi| 2 +-
doc/ref/api-data.texi
>> These snippets fail to evaluate. Could you check?
>
> I can confirm. Would be worth fixing.
I have opened a separate bug report
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40235 for this.
> Applied, thanks!
Thanks!
signature.asc
Description: PGP signature
Two of the code snippets in "(guile) sxml-match" fail to evaluate. They
are:
* The first snippet in the "Matching the Unmatched Attributes" subsection
@lisp
(sxml-match '(a (@@ (z 1) (y 2) (x 3)) 4 5 6)
((a (@@ (y ,www) . ,qqq) ,t ,u ,v)
(list www qqq t u v)))
@end lisp
* The snippet in th
* doc/ref/scheme-using.texi (Profile Commands): Mention (ice-9 time)
module path.
---
doc/ref/scheme-using.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index ac265fcca..31981cb5d 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/r
* doc/ref/api-data.texi (String Constructors): Document default
delimiter of the string-join function.
---
doc/ref/api-data.texi | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index a6b09c478..3dd5109c4 100644
--- a/doc/ref/
* doc/ref/web.texi (HTTP Headers): Fix minor typo.
---
doc/ref/web.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index 2d07dd7b1..31630def7 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -774,7 +774,7 @@ The MD5 digest of a re
* doc/ref/web.texi (HTTP Headers): Improve punctuation in content-range
HTTP header documentation.
---
doc/ref/web.texi | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index 31630def7..93cd0214f 100644
--- a/doc/ref/web.texi
+++ b/
A few minor documentation fixes and improvements follow.
Arun Isaac (4):
doc: Fix minor typo in the HTTP headers documentation.
doc: Improve content-range HTTP header documentation.
doc: Document default delimiter of string-join.
doc: Mention (ice-9 time) module path.
doc/ref/api
Suppose I start guile to listen on a unix socket /tmp/guile like so:
$ guile --listen=/tmp/guile
When I quit guile, the socket file still remains. The next time I start
guile to listen on /tmp/guile, guile errors out with the following
error. It would be better if guile deleted the socket file o
t; subsection
@lisp
(sxml-match '(e 3 4 5)
((e (@@ (z (,d 1))) ,a ,b ,c) (list d a b c)))
@end lisp
These snippets fail to evaluate. Could you check?
Thanks!
From 6e31e3fe1fd2b537d4a02dbcfccbb03e0d20e804 Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Tue, 24 Mar 2020 01:45:32 +0530
Subj
* doc/ref/r6rs.texi (rnrs io ports): Fix order of arguments to seek in
port-position and set-port-position! documentation.
---
doc/ref/r6rs.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/r6rs.texi b/doc/ref/r6rs.texi
index 9d326ff09..3f36fef0f 100644
--- a/doc
* doc/ref/web.texi (HTTP Headers): Fix minor typo.
---
doc/ref/web.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index c8fc488b7..c11ed32fa 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -791,7 +791,7 @@ The MIME type of a res
> The macros (such as GUILE_PKK) are provided by the Guile package, so I
> think that’s expected.
I forgot to mention. I already have guile in my system profile (the
default one outside any environment created using `guix
environment'). `which guile' outputs the following:
/run/current-system/p
> --8<---cut here---start->8---
> detlef:~/src/guile-debbugs> ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for ga
> [albinus@BRONB4NHFYN1 guile-debbugs]$ ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... ye
>> If you'd like to investigate further, I'd be glad to give you
>> pointers and advice, but it's not a project for the faint-hearted :-/
I am faint-hearted and do not wish to pursue this further. :-P I just
thought it might be useful to report. Should I close this bug report, or
leave it open f
Guile's auto compile fails to recompile when included source files
change.
For example, I have two source files -- foo.scm and bar.scm. foo.scm
includes bar.scm using `include'. When I run foo.scm for the first time,
it is auto compiled and run correctly. But, if I modify bar.scm and run
foo.scm
* module/web/client.scm (request): Rename to http-request, add a
docstring, and export it.
(http-get, http-head, http-post, http-put, http-delete, http-trace,
http-options): Update docstring.
* doc/ref/web.texi (Web Client): Document http-request.
---
doc/ref/web.texi | 40 -
mod
>> Yes, exporting 'request' alone would serve my purpose, although
>> 'define-http-verb' would make my script much shorter. But, I'll leave it
>> to your judgement. Should I send a new patch exporting 'request' alone?
>
> Could you do that? The ‘request’ procedure can simply be made public
> and
All examples in "(guile) sxml-match" use square parentheses around each
match clause. However, in the subsection "Guards in Patterns" alone, the
example has round parentheses. I think it would be nice to use round
parentheses consistently in all examples so that sxml-match and match
have the same
Hi,
I have made all the changes you suggested. Patch follows.
Thanks.
Arun Isaac (1):
doc: Document (ice-9 match) macros.
doc/ref/match.texi | 92 --
1 file changed, 90 insertions(+), 2 deletions(-)
--
2.15.1
* doc/ref/match.texi: Document match-lambda, match-lambda*, match-let,
match-let* and match-letrec.
---
doc/ref/match.texi | 92 --
1 file changed, 90 insertions(+), 2 deletions(-)
diff --git a/doc/ref/match.texi b/doc/ref/match.texi
index 12e
>> +Match each variable to the corresponding expression, and evaluate the
>> +body with all matched variables in scope. Raise an error if any of the
>> +expressions fail to match. @code{match-let} is analogous to named let
>
> It's only analogous to a named let if a variable name is inserted
> i
* doc/ref/api-peg.texi (PEG Internals): Fix minor typo.
---
doc/ref/api-peg.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-peg.texi b/doc/ref/api-peg.texi
index cbe3edd34..82e2758b4 100644
--- a/doc/ref/api-peg.texi
+++ b/doc/ref/api-peg.texi
@@ -1012,7 +1012,
> Having looked into this a bit more, I wonder if Guile should even try to
> set the port encoding itself. As far as I can tell, there's no way to
> know the encoding of the response payload in the general case, without
> knowledge of the specific MIME media type. We could teach Guile about
> "a
Mark H Weaver writes:
>> If you think it's not a good idea to include http-patch in guile, maybe
>> we can export define-http-verb and/or request so that it is easy for
>> users to create their own custom HTTP methods. WDYT?
>
> I would prefer to export the 'request' procedure from (web client),
Mark H Weaver writes:
> Since PATCH was removed from HTTP over 18 years ago, and is clearly not
> valid HTTP/1.1, I wonder if it makes sense to add this.
> Do you have a use case where you need it?
Yes, I was using the PowerDNS HTTP API, and some of their API requests
need the PATCH method.
ht
Mark H Weaver writes:
About undefined?: That was a typo. I mentioned that in a later message.
> It's nonsensical to ask whether a given object is "unspecified". When
> the Scheme standards say that the result of a computation is an
> unspecified value, that means that *any* Scheme object could
Mark H Weaver writes:
> Would you be willing to assign the copyright to the Free Software
> Foundation, so that we could install it in Guile?
Yes, sure. I'd be happy to assign copyright to the FSF. Let me know what
I should do.
* module/web/client.scm (http-patch): New HTTP verb.
* doc/ref/web.texi (Web Client): Document it.
---
doc/ref/web.texi | 1 +
module/web/client.scm | 12
2 files changed, 13 insertions(+)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index 07da5b64b..7f119ba99 100644
--- a/
* doc/ref/data-rep.texi: Document unspecified?.
---
doc/ref/data-rep.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/ref/data-rep.texi b/doc/ref/data-rep.texi
index bb7f74afe..f179a3560 100644
--- a/doc/ref/data-rep.texi
+++ b/doc/ref/data-rep.texi
@@ -470,6 +470,9 @@ check to see
I intended to document unspecified?. I have somehow gotten confused and
ended up specifying it as undefined?. Disregard this patch. I will send
a new one.
* doc/ref/data-rep.texi: Document undefined?.
---
doc/ref/data-rep.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/ref/data-rep.texi b/doc/ref/data-rep.texi
index bb7f74afe..ed3a5a522 100644
--- a/doc/ref/data-rep.texi
+++ b/doc/ref/data-rep.texi
@@ -470,6 +470,9 @@ check to see if
* doc/ref/match.texi: Document match-lambda, match-lambda*, match-let,
match-let* and match-letrec.
---
doc/ref/match.texi | 65 --
1 file changed, 63 insertions(+), 2 deletions(-)
diff --git a/doc/ref/match.texi b/doc/ref/match.texi
index 12e
* module/web/response.scm (text-content-type?): Recognize JSON content
type as text.
---
module/web/response.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/module/web/response.scm b/module/web/response.scm
index 06e1c6dc1..679304c4d 100644
--- a/module/web/response.scm
+++ b/module/web/
* doc/ref/api-peg.texi (PEG Parsing): Mention (ice-9 peg) module path.
---
doc/ref/api-peg.texi | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/doc/ref/api-peg.texi b/doc/ref/api-peg.texi
index 0e16aab7e..cbe3edd34 100644
--- a/doc/ref/api-peg.texi
+++ b/doc/ref/api
* doc/ref/api-io.texi (Ports): Convert `close' ref to xref.
---
doc/ref/api-io.texi | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/doc/ref/api-io.texi b/doc/ref/api-io.texi
index 9bd78d229..24890a12e 100644
--- a/doc/ref/api-io.texi
+++ b/doc/ref/api-io.texi
@@ -115,9 +11
Currently, in info, it is rendered as "See also see close". Notice the
double occurrence of "see".
Arun Isaac (1):
Convert `close' ref to xref.
doc/ref/api-io.texi | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.14.2
> Thanks, fixed. Patches welcome in the future too :)
Sure, thanks!
Hi,
In the second line of the argument specification of scheme procedure
`fold-layout', "handler-pair" is misspelt as "bandler-pair".
It says:
binding := ( ...)
It should be:
binding := ( ...)
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
53 matches
Mail list logo
