From: jgart via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 57808@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>
Subject: bug#57808: [PATCH] string-fun: Fix typo
Date: Wed, 14 Sep 2022 13:14:21 -0500 [thread overview]
Message-ID: <20220914181421.28913-1-jgart@dismail.de> (raw)
---
module/ice-9/string-fun.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/module/ice-9/string-fun.scm b/module/ice-9/string-fun.scm
index 03e0238fa..592b49e20 100644
--- a/module/ice-9/string-fun.scm
+++ b/module/ice-9/string-fun.scm
@@ -30,7 +30,7 @@
;;;;
;;;
-;;; Various string funcitons, particularly those that take
+;;; Various string functions, particularly those that take
;;; advantage of the "shared substring" capability.
;;; FIXME Document these functions in Miscellaneous String Operations::
;;; in doc/ref/api-data.texi.
--
2.37.3
next reply other threads:[~2022-09-14 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 18:14 jgart via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2022-09-17 11:45 ` bug#57808: [PATCH] string-fun: Fix typo lloda
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=20220914181421.28913-1-jgart@dismail.de \
--to=bug-guile@gnu.org \
--cc=57808@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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).