From: Ian Price <ianprice90@googlemail.com>
To: Josep Portella Florit <jpf@primfilat.com>
Cc: 15136-done@debbugs.gnu.org, 15136@debbugs.gnu.org
Subject: bug#15136: get-string-all documentation
Date: Mon, 19 Aug 2013 22:31:51 +0100 [thread overview]
Message-ID: <87ioz12wqg.fsf@Kagami.home> (raw)
In-Reply-To: <1376945933.31074.11.camel@qwghlm> (Josep Portella Florit's message of "Mon, 19 Aug 2013 22:58:53 +0200")
Josep Portella Florit <jpf@primfilat.com> writes:
> In the documentation for get-string-all, on module (rnrs io ports), it
> says:
>
> Scheme Procedure: get-string-all textual-input-port count
>
Yes, a silly little oversight. Thanks for the report. It's fixed in
stable.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
prev parent reply other threads:[~2013-08-19 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:58 bug#15136: get-string-all documentation Josep Portella Florit
2013-08-19 21:31 ` Ian Price [this message]
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=87ioz12wqg.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=15136-done@debbugs.gnu.org \
--cc=15136@debbugs.gnu.org \
--cc=jpf@primfilat.com \
/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).