From: Mark H Weaver <mhw@netris.org>
To: Josep Portella Florit <jpf@primfilat.com>
Cc: 15152-done@debbugs.gnu.org
Subject: bug#15152: put-char documentation
Date: Fri, 13 Sep 2013 00:10:48 -0400 [thread overview]
Message-ID: <87fvt9l5tj.fsf@tines.lan> (raw)
In-Reply-To: <1377093680.9407.1.camel@qwghlm> (Josep Portella Florit's message of "Wed, 21 Aug 2013 16:01:20 +0200")
Josep Portella Florit <jpf@primfilat.com> writes:
> There is another little error in `doc/ref/api-io.texi'. The
> documentation for put-char ends abruptly:
>
> @deffn {Scheme Procedure} put-char port char
> Writes @var{char} to the port. The @code{put-char} procedure returns
> @end deffn
>
> It should be:
>
> @deffn {Scheme Procedure} put-char port char
> Writes @var{char} to the port. The @code{put-char} procedure returns
> an unspecified value.
> @end deffn
Fixed in 803c087e6b72f59ed9e529c1e1ca4fbe34e8eda5.
Thanks!
Mark
prev parent reply other threads:[~2013-09-13 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:01 bug#15152: put-char documentation Josep Portella Florit
2013-09-13 4:10 ` Mark H Weaver [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=87fvt9l5tj.fsf@tines.lan \
--to=mhw@netris.org \
--cc=15152-done@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).