From: Georgi Kirilov <kirilov.georgi.s@gmail.com>
To: 25512@debbugs.gnu.org
Cc: Georgi Kirilov <kirilov.georgi.s@gmail.com>
Subject: bug#25512: [PATCH] Fix typo in keywords documentation
Date: Mon, 23 Jan 2017 11:44:37 +0200 [thread overview]
Message-ID: <20170123094437.8765-1-kirilov.georgi.s@gmail.com> (raw)
* doc/ref/api-data.texi (Keyword Read Syntax): Fix typo
---
doc/ref/api-data.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index 1b3170e4f..4316fc0f5 100644
--- a/doc/ref/api-data.texi
+++ b/doc/ref/api-data.texi
@@ -5412,7 +5412,7 @@ of the form @code{:NAME} are read as symbols, as required by R5RS.
@cindex SRFI-88 keyword syntax
-If the @code{keyword} read option is set to @code{'postfix}, Guile
+If the @code{keywords} read option is set to @code{'postfix}, Guile
recognizes the SRFI-88 read syntax @code{NAME:} (@pxref{SRFI-88}).
Otherwise, tokens of this form are read as symbols.
--
2.11.0
next reply other threads:[~2017-01-23 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 9:44 Georgi Kirilov [this message]
2017-02-12 21:05 ` bug#25512: [PATCH] Fix typo in keywords documentation 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=20170123094437.8765-1-kirilov.georgi.s@gmail.com \
--to=kirilov.georgi.s@gmail.com \
--cc=25512@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).