From 7cf2c9947ce0a5529b15835b7e1eecb30a2e68c2 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 29 Sep 2026 14:06:59 -0300 Subject: Not-found failures say it once, in plain words: grep: pattern not found, callers not found The ENOENT that 9ns reads from a failure's words came from a tacked-on suffix, grep: no match, not found, definition: nothing found, not found, no shell "x", not found. They now say it once: grep: pattern not found, find: name not found, Callers: callers not found, definition: not found, shell "x" not found (...). Co-Authored-By: Claude Opus 5.5 --- docs/fs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/fs.md') diff --git a/docs/fs.md b/docs/fs.md index 4b772c18..b7d1d27e 100644 --- a/docs/fs.md +++ b/docs/fs.md @@ -258,7 +258,7 @@ back changes nothing; a setting the frontend cannot show (`Lift`, (EINVAL: a request this build cannot take), and so is a builtin only the GUI has (`Fonts`), written to an `exec` too, where it would otherwise run as a shell command; a `Shell` or `Tty` naming no -shell says `no shell "x", not found` (ENOENT); a `DumpDir` whose last +shell says `shell "x" not found` (ENOENT); a `DumpDir` whose last directory is missing has it made at the Dump, and one further up missing says `Dump : no such directory` (ENOENT), one that is no directory (`/dev/null`) `Dump /dev/null/pardes-