From: Vagrant Cascadian <vagrant@debian.org>
To: guile-devel@gnu.org
Cc: David Pirotte <david@altosw.be>
Subject: [PATCH] guile-lib: src/logger/logger.scm: Fix spelling of "invocation".
Date: Thu, 02 Dec 2021 14:13:38 -0800 [thread overview]
Message-ID: <87lf12venh.fsf@ponder> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]
Originally sent to guile-user, as the README suggested bugs should go
there, though I see guile-devel mentioned on
https://www.nongnu.org/guile-lib/dev/
Maybe the README should be updated?
Thanks!
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-src-logger-logger.scm-Fix-spelling-of-invocation.patch --]
[-- Type: text/x-diff, Size: 942 bytes --]
From 90c49101ee242ccb9a449108f9c95ee14aaf5302 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Thu, 2 Dec 2021 13:54:37 -0800
Subject: [PATCH] src/logger/logger.scm: Fix spelling of "invocation".
---
src/logging/logger.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/logging/logger.scm b/src/logging/logger.scm
index 7ff4f43..d88cdf8 100644
--- a/src/logging/logger.scm
+++ b/src/logging/logger.scm
@@ -291,7 +291,7 @@ This optional parameter must be a function that takes three arguments:
the log level, the time (as from @code{current-time}), and the log string
itself. The function must return a string representing the formatted log.
-Here is an example invokation of the default formatter, and what it's
+Here is an example invocation of the default formatter, and what it's
output looks like:
@lisp
(default-log-formatter 'CRITICAL
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2021-12-02 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 22:13 Vagrant Cascadian [this message]
2024-03-25 4:12 ` [PATCH] guile-lib: src/logger/logger.scm: Fix spelling of "invocation" David Pirotte
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=87lf12venh.fsf@ponder \
--to=vagrant@debian.org \
--cc=david@altosw.be \
--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).