From c3c3ef27ede2f69ef4f8c6acb10808f02ee46bb2 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 29 Sep 2026 11:48:32 -0300 Subject: A builtin or setting this build lacks is refused GUI-only, from an exec too On a terminal, Fonts written to an exec was no builtin there, so it ran as a shell command and ended exit 127; ctl said unknown control message. Both now say Fonts is GUI-only, invalid here (a builtin another platform's build has, not in this build). Co-Authored-By: Claude Opus 5.5 --- docs/fs.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/fs.md b/docs/fs.md index 5de73b86..70a76c92 100644 --- a/docs/fs.md +++ b/docs/fs.md @@ -253,7 +253,9 @@ takes (`Verbose on`, `WindowOpacity 70`, `PanelSlide off`, `DumpDir `, `LocationsConfig ...`), so writing what it reads back changes nothing; a setting the frontend cannot show (`Lift`, `GripWidth` on a terminal) is refused as `Lift is GUI-only, invalid here` -(EINVAL: a request this build cannot take); a `Shell` or `Tty` naming no +(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 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 -- cgit v1.3