From: Felix Lechner via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 68624@debbugs.gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: bug#68624: [PATCH] Decode errno for encoding errors.
Date: Sat, 20 Jan 2024 19:38:26 -0800 [thread overview]
Message-ID: <20240121034401.17992-2-felix.lechner@lease-up.com> (raw)
* libguile/strings.c (scm_encoding_error): Decode errno.
---
Hi,
Even experienced users do not memorize errno values. [1][2] Why not
decode them as a courtesy?
Kind regards
Felix Lechner
[1] https://debbugs.gnu.org/62590
[2] https://debbugs.gnu.org/59510
libguile/strings.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libguile/strings.c b/libguile/strings.c
index 5eebb3300..ba69bd65e 100644
--- a/libguile/strings.c
+++ b/libguile/strings.c
@@ -1468,7 +1468,7 @@ scm_encoding_error (const char *subr, int err, const char *message,
scm_throw (scm_encoding_error_key,
scm_list_n (scm_from_latin1_string (subr),
scm_from_latin1_string (message),
- scm_from_int (err),
+ scm_strerror (err),
port, chr,
SCM_UNDEFINED));
}
base-commit: d8df317bafcdd9fcfebb636433c4871f2fab28b2
--
2.41.0
reply other threads:[~2024-01-21 3:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240121034401.17992-2-felix.lechner@lease-up.com \
--to=bug-guile@gnu.org \
--cc=68624@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
/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).