From: Felix Lechner via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 69288@debbugs.gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: bug#69288: [PATCH] Fix typo in documentation for output buffering.
Date: Tue, 20 Feb 2024 07:50:58 -0800 [thread overview]
Message-ID: <20240220155058.23900-1-felix.lechner@lease-up.com> (raw)
* doc/ref/api-control.texi (Buffering): Fix typo.
---
doc/ref/api-io.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-io.texi b/doc/ref/api-io.texi
index e263e2985..38b553b80 100644
--- a/doc/ref/api-io.texi
+++ b/doc/ref/api-io.texi
@@ -754,7 +754,7 @@ line-buffered ports, respectively. @xref{File Ports}, for more.
Any buffered output data will be written out when the port is closed.
To make sure to flush it at specific points in your program, use
-@code{force-otput}.
+@code{force-output}.
@findex fflush
@deffn {Scheme Procedure} force-output [port]
base-commit: 9e0f03c5fd36764827c8bb03887f14640c883b70
--
2.41.0
reply other threads:[~2024-02-20 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240220155058.23900-1-felix.lechner@lease-up.com \
--to=bug-guile@gnu.org \
--cc=69288@debbugs.gnu.org \
--cc=felix.lechner@lease-up.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).