From: "Ludovic Courtès" <ludo@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 72208@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#72208: [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi
Date: Sat, 26 Oct 2024 19:27:04 +0200 [thread overview]
Message-ID: <87a5eqvkpj.fsf__21455.4304651514$1729963680$gmane$org@gnu.org> (raw)
In-Reply-To: <87y15wjeca.fsf@web.de> (Arne Babenhauserheide's message of "Sat, 20 Jul 2024 17:03:01 +0200")
Hello,
"Dr. Arne Babenhauserheide" <arne_bab@web.de> skribis:
> From 6838e4da9712425e7e45805a73731bb399d90a86 Mon Sep 17 00:00:00 2001
> From: Arne Babenhauserheide <arne_bab@web.de>
> Date: Sat, 20 Jul 2024 15:03:15 +0200
> Subject: [PATCH] doc: reference ice-9, scheme, and srfi
>
> * doc/ref/tour.texi (Using Modules): reference ice-9, scheme, and srfi.
Good idea!
> +Most provided modules use prefixes based on their origin:
> +
> +@itemize @bullet
> +@item @code{ice-9} includes guile-specific modules: the standard library of Guile. @xref{Status, History of ice-9, History of ice-9}
s/guile/Guile/
Also: please leave two spaces after an end-of-sentence period and add a
semicolon at the end of the line.
> +@item @code{rnrs} and @code{scheme} include modules from the RnRS standard (@url{https://standards.scheme.org/}). @xref{R7RS Support} and @xref{R6RS Support}
s/RnRS standard/Scheme standards/
Likewise, semicolon at the end of the line
> +@item @code{srfi} includes Scheme Requests For Implementation; SRFI’s (@url{https://srfi.schemers.org/}). @xref{SRFI Support}
Rather:
… includes @uref{https://srfi.schemers.org/, Scheme Requests for
Implementation or ``SRFIs''} (@pxref{SRFI Support});
> +@item Some larger features have their own prefix. These include @code{web} (@pxref{Web}), @code{oop} (@xref{GOOPS}), @code{sxml} (@pxref{SXML}), and @code{language} (@pxref{Other Languages}).
s/@xref{GOOPS}/@pxref{GOOPS}/ (since it’s in parentheses)
Fine with me with these changes!
Ludo’.
prev parent reply other threads:[~2024-10-26 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 13:11 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi Dr. Arne Babenhauserheide
[not found] ` <handler.72208.B.17214811119924.ack@debbugs.gnu.org>
2024-07-20 15:03 ` bug#72208: " Dr. Arne Babenhauserheide via Bug reports for GUILE, GNU's Ubiquitous Extension Language
[not found] ` <87y15wjeca.fsf@web.de>
2024-10-26 17:27 ` Ludovic Courtès [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='87a5eqvkpj.fsf__21455.4304651514$1729963680$gmane$org@gnu.org' \
--to=ludo@gnu.org \
--cc=72208@debbugs.gnu.org \
--cc=arne_bab@web.de \
--cc=guile-devel@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).