From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: 9front@9front.org
Subject: [9front] ape/_errno: ENOENT
Date: Tue, 04 Jan 2022 20:50:49 +0100 [thread overview]
Message-ID: <87tuej2sbq.fsf@turtle-trading.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
Tcl checks errno==ENOENT for its equivalent of "rm -f", but APE does not
recognize the errstr for that.
If somebody knows where the code for this is, we could add comment with
a pointer to that source. Also, is there a way to find more omissions
like this?
[-- Attachment #2.1: Type: text/plain, Size: 310 bytes --]
from postmaster@4ess:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/x-diff
Content-Disposition: inline;
filename="0003-ape-_errno.c-(map)-add-another-ENOENT.patch"
[-- Attachment #2.2: 0003-ape-_errno.c-(map)-add-another-ENOENT.patch.suspect --]
[-- Type: application/octet-stream, Size: 655 bytes --]
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Date: Sat, 25 Dec 2021 13:59:59 +0000
Subject: [PATCH] ape/_errno.c (map): add another ENOENT
Many programs check this particular errno.
---
diff dd7ad4725c5dfb26ad44e8e4206116f96f054ba4 f96fae96efebf3eb7917e2c0b55439db2b242f79
--- a/sys/src/ape/lib/ap/plan9/_errno.c Fri Dec 10 21:47:09 2021
+++ b/sys/src/ape/lib/ap/plan9/_errno.c Sat Dec 25 14:59:59 2021
@@ -102,6 +102,8 @@
{EOPNOTSUPP, "operation not supported"},
{EADDRINUSE, "address in use"},
{EGREG, "unnamed error message"},
+
+ {ENOENT, "No such file"},
};
#define NERRMAP (sizeof(map)/sizeof(struct errmap))
--
1.0
next reply other threads:[~2022-01-04 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 19:50 Benjamin Riefenstahl [this message]
2022-01-05 19:13 ` cinap_lenrek
2022-01-06 13:35 ` Benjamin Riefenstahl
2022-01-06 16:27 ` ori
2022-01-06 17:32 ` Benjamin Riefenstahl
2022-01-06 20:24 ` Xiao-Yong Jin
2022-01-07 10:09 ` Benjamin Riefenstahl
2022-01-10 1:55 ` 有澤 健治
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuej2sbq.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=9front@9front.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 NNTP newsgroup(s).