From: Fulbert <fulbert@bluewin.ch>
To: 57776@debbugs.gnu.org
Subject: bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag).
Date: Tue, 13 Sep 2022 18:28:40 +0200 [thread overview]
Message-ID: <YyCvuFDPtHgT+hza@bluewin.ch> (raw)
---
doc/ref/compiler.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/compiler.texi b/doc/ref/compiler.texi
index 27964e881..865a77607 100644
--- a/doc/ref/compiler.texi
+++ b/doc/ref/compiler.texi
@@ -1120,7 +1120,7 @@ especially in cases when we know that we can just update the intmap in
place. As an example, say we have an intmap mapping the integers 1 to
100 to the integers 42 to 141. Let's say that we want to transform this
map by adding 1 to each value. There is already an efficient
-@code{intmap-map} procedure in the @code{(language cps utils}) module,
+@code{intmap-map} procedure in the @code{(language cps utils)} module,
but if we didn't know about that we might do:
@example
--
2.37.3
next reply other threads:[~2022-09-13 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 16:28 Fulbert [this message]
2022-10-01 13:50 ` bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag) 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=YyCvuFDPtHgT+hza@bluewin.ch \
--to=fulbert@bluewin.ch \
--cc=57776@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).