From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: guile-devel@gnu.org
Subject: [PATCH]: Fix a documentation for SRFI-171
Date: Fri, 01 May 2020 16:55:42 +0200 [thread overview]
Message-ID: <a2846e63-0231-48b5-a830-aac22502fce1@www.fastmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
Hi yall!
I managed to bork the documentation in my patch that added SRFI-171 to guile. Here is the two-line patch to fix it.
Sorry if it caused anyone any trouble. I just built guile from head on mac os x with this patch applied, an none of the warnings were my fault.
--
Linus Björnstam
[-- Attachment #2: 0001-Fix-documentation-for-srfi-171.patch --]
[-- Type: application/octet-stream, Size: 1375 bytes --]
From 5124d2a429a408f5b6fcd3d6780b047aacaaae48 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Linus=20Bj=C3=B6rnstam?= <linus@Linuss-iMac.local>
Date: Fri, 1 May 2020 15:11:25 +0200
Subject: [PATCH] Fix documentation for srfi-171 * doc/ref/srfi-modules.texi
(SRFI-171): Fix broken documentation.
---
doc/ref/srfi-modules.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/srfi-modules.texi b/doc/ref/srfi-modules.texi
index fd190799c..9de8396d7 100644
--- a/doc/ref/srfi-modules.texi
+++ b/doc/ref/srfi-modules.texi
@@ -5764,7 +5764,7 @@ and SRFI-158-styled generators respectively.
@deffnx {Scheme Procedure} port-transduce xform f identity reader port
Same as @code{list-reduce} but for ports. Called without a port, it
-reduces over the results of applying @var{(reader)} until the
+reduces over the results of applying @var{reader} until the
EOF-object is returned, presumably to read from
@code{current-input-port}. With a port @var{reader} is applied to
@var{port} instead of without any arguments. If @var{identity} is
@@ -6010,7 +6010,7 @@ be used to generalize something like @code{tsegment}:
@example
;; This behaves exactly like (tsegment 4).
(list-transduce (tbatch (ttake 4) rcons) rcons (iota 10))
-@result {} ((0 1 2 3) (4 5 6 7) (8 9))
+@result{} ((0 1 2 3) (4 5 6 7) (8 9))
@end example
@end deffn
--
2.25.0
next reply other threads:[~2020-05-01 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:55 Linus Björnstam [this message]
2020-05-17 21:13 ` [PATCH]: Fix a documentation for SRFI-171 Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2846e63-0231-48b5-a830-aac22502fce1@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).