From: Arun Isaac <arunisaac@systemreboot.net>
To: 29310@debbugs.gnu.org
Subject: bug#29310: [PATCH 1/1] Convert `close' ref to xref.
Date: Thu, 16 Nov 2017 03:43:12 +0530 [thread overview]
Message-ID: <d1acb14c.AEMASbC5k18AAAAAAAAAAAP_olwAAAACwQwAAAAAAAW9WABaDLwG@mailjet.com> (raw)
In-Reply-To: <01cbc0d8.AEAASbQEsIwAAAAAAAAAAAOtoJAAAAACwQwAAAAAAAW9WABaDLtx@mailjet.com>
* 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 +115,8 @@ Return @code{#t} if @var{x} is an output port, otherwise return
Close the specified port object. Return @code{#t} if it successfully
closes a port or @code{#f} if it was already closed. An exception may
be raised if an error occurs, for example when flushing buffered output.
-@xref{Buffering}, for more on buffered output. See also @ref{Ports and
-File Descriptors, close}, for a procedure which can close file
-descriptors.
+@xref{Buffering}, for more on buffered output. @xref{Ports and File
+Descriptors, close}, for a procedure which can close file descriptors.
@end deffn
@deffn {Scheme Procedure} port-closed? port
--
2.14.2
next prev parent reply other threads:[~2017-11-15 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 22:10 bug#29310: [PATCH 0/1] `close-port' documentation: Convert `close' ref to xref Arun Isaac
2017-11-15 22:13 ` Arun Isaac [this message]
2017-11-22 15:07 ` bug#29310: [PATCH 1/1] " 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=d1acb14c.AEMASbC5k18AAAAAAAAAAAP_olwAAAACwQwAAAAAAAW9WABaDLwG@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=29310@debbugs.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).