ThemeSel is Themes and FontSel is Fonts; the old words still work in init files and dumps

The user asked for the plainer words. Every use is renamed: the
builtins, leader paths, /commands, the docs and tutor, tests, and the
themesel golden, re-recorded. An init file's ThemeSel or FontSel runs
the new word and says `ThemeSel: renamed to Themes`, as ColumnTags is
said; a dump naming an output pane by the old word restores it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

7 files changed, 11 insertions, 11 deletions

diff --git a/docs/config.md b/docs/config.md
index 96281cd5..9d7446f1 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -96,7 +96,7 @@ The SDL GUI also has `WindowOpacity`, which takes one argument.
 `builtins.Board.enabled` holds, and that build has no config file.)
 
 `Theme <name>` wants one of the names in the compiled ring. Do not derive the
-spelling — read it off `ThemeSel` (`SPC t t`), which lists every one as the
+spelling — read it off `Themes` (`SPC t t`), which lists every one as the
 exact `Theme <name>` line that selects it. `slug` in `tools/gen_themes.zig`
 lowercases, folds punctuation runs to a single `_` and then TRIMS leading and
 trailing ones (`penumbra+.toml` is `penumbra`, not `penumbra_`), and every
@@ -109,7 +109,7 @@ project gains or loses a file. A name that is not in the ring is ignored.
 The fifteen [native Pardes themes](themes.md) lead the ring: `orchard` (the
 default), `dusk`, `ink`, `paper`, `daybreak`, `atelier`, `forge`, `lagoon`,
 `solarium`, `spectrum`, `harvest`, `clay`, `forge_black`, `forge_soft`, and
-`orchard_black`. `ThemeSel` lists them first under Pardes themes, followed by
+`orchard_black`. `Themes` lists them first under Pardes themes, followed by
 a separate legacy/imported section. They add coordinated
 focus, search, diagnostic and terminal colors; `ink` and `daybreak` are high
 contrast dark and light options. The original `helix`, `dark` and `acme`
@@ -391,7 +391,7 @@ asked for one. Neither reaches the child as a keystroke, so an application
 that would otherwise answer Ctrl-V by reading the system clipboard itself
 never gets the chance to read the wrong thing.
 
-`Font` and `FontSel` exist ONLY in the SDL GUI and native macOS builds — a
+`Font` and `Fonts` exist ONLY in the SDL GUI and native macOS builds — a
 terminal's font belongs to its emulator and a browser's to the page — so a
 `Font` line is one of the silently-ignored ones everywhere else. Both builds
 resolve the name by walking the font directories on every lookup, so a face
diff --git a/docs/design.typ b/docs/design.typ
index 639884a9..ed2bbb94 100644
--- a/docs/design.typ
+++ b/docs/design.typ
@@ -2010,7 +2010,7 @@ one pair per theme, and the three per-button tints and the dimmed extra cursors
 are mixed off it, so what stays fixed is the distinction between buttons and not
 the colours. `NextColor` browses the ring one
 step at a time — at 228 it is no longer how you REACH one —
-`Theme <name>` jumps to one and `ThemeSel` (`SPC t t`) lists them all into an
+`Theme <name>` jumps to one and `Themes` (`SPC t t`) lists them all into an
 output buffer whose rows are those very commands — execute a row (Tab, middle
 click) and the theme goes on; n/N select such a row WHOLE, since a command
 line holds no place to pick out of it — the third grain of that motion, the
diff --git a/docs/fs.md b/docs/fs.md
index dedfe94f..ceca1dd9 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -274,7 +274,7 @@ argument to a builtin that takes none, or none to one that needs it (`Msg`,
 `Mount`, `Find`, a setting's value but a switch's, which flips bare);
 `bad value in control message "X"` for a setting's value it does not take
 (for `Theme`, naming the themes that share the name's first letter, since
-all of them, `ThemeSel`'s list, are too many for an error);
+all of them, `Themes`'s list, are too many for an error);
 and `not a session control message "X": write it to pane/<n>/ctl` or `not
 a window control message "X": write it to /ctl` for a word of the other ctl. 9ns maps them all to EINVAL, and a write
 refused here has done nothing. A line that then fails as it runs fails the
diff --git a/docs/helix-keys.md b/docs/helix-keys.md
index 5d89ba92..b1035ad6 100644
--- a/docs/helix-keys.md
+++ b/docs/helix-keys.md
@@ -135,7 +135,7 @@ language-backend queries, and the shell pipe.
 | `SPC y` `SPC Y` `SPC p` `SPC P` `SPC R` | helix's clipboard menu on helix's own letters: yank the selection to the system clipboard (`ClipYank`) or the PRIMARY selection alone (`ClipYankMain`), paste the system clipboard after (`ClipPaste`) / before (`ClipPasteBefore`) the selection, replace the selection with it (`ClipReplace`) | the same as `"+y`, `"+p`, `"+P`, `"+R`: register `+` (and `*`) IS the desktop's clipboard, the only register that reaches it. `SPC y` writes `+` alone, as helix's does, not the default register too. Builtins rather than bare chords because a leader path names a builtin: they land in Help's index and are executable words like every other verb. The clipboard holds one text, so N values go out joined by newlines, as helix sends them. On a tty the write is OSC 52 out and the READ is OSC 52 back, which many terminals refuse or gate — so `SPC y` works there and `SPC p` can be a no-op | out of corpus |
 | a paste from the OUTER terminal | one `Event.paste`, spliced in at the cursor | the tty shell enables bracketed paste and coalesces `paste_start`..`paste_end` into a single event; before that the bytes arrived as individual key presses and normal mode RAN them, which is how a pasted `d` deleted a line. The bytes deliberately never enter the yank register — clipboard and default register are separate stores in both directions | pardes-specific |
 | `/` (any pane) | pardes' own plain-substring search into a `+Search` output buffer: the pattern is typed on a line of its own on the pane's notice band, Enter fills the buffer, and its rows are ordinary look targets. Enter also GOES to the first row — the buffer is focused and then the step `n` is and the look Enter is run in it (`Pardes.lookFirstHit`), so `/foo` lands on the first hit with the matched span selected. A pattern that matched nothing opens its empty buffer and moves nothing | KEEP, do not touch; not in the corpus (helix `/` is regex search). Find and Grep answer with OTHER files and deliberately do NOT jump. The stepping half is the next row | pardes-specific |
-| `n` / `N` (any pane) | MOTION, not a jump: move the SELECTION to the next / previous look-able text and open NOTHING. Enter — the look chord — on what it leaves selected is what opens it | KEEP, do not touch; not in the corpus (helix's `n`/`N` walk regex search hits). What a step selects is the pane's GRAIN (`output_pane.Grain`, read in `Pardes.lookSpanIn`): in FREE TEXT — a terminal, a file, a PDF, a prose answer buffer — the largest whitespace-delimited run `look.resolve` can act on (`look.lookableSpan`, wrapper punctuation peeled off both ends), several to a line; in a RESULTS BUFFER one stop per ROW, the largest run its head resolves as (`look.lookableLineSpan`), because a row there IS one location and the words after it are the match rather than a second place to go; in a COMMAND list the whole line. The walk is a RING across PANES: every pane that has performed a Look, most recent first (`Pardes.look_src`), then the output buffers that have not, newest first, and only when both are empty the active pane. Exhausting a pane enters the next at its first (forward) / last (backward) span and the end wraps to the start, so `N` is the exact inverse of `n`. What it lands on becomes an EXPLICIT `vsel` with the cursor on its FIRST column, in the pane the walk focuses. ONE motion in every pane kind and every buffer kind — a PDF steps the `+Search` buffer its own search filled, `n` to select the row and Enter to jump. The single thing a buffer may change is that grain, and it changes it by BEING a kind of buffer rather than by a branch: `output_pane.Traits.steps` (a list of locations) makes a step take one row at a time, and `Traits.commands` makes it take the WHOLE LINE, because a command list (`ThemeSel`/`FontSel`) holds words to run and there is no path inside `Theme gruvbox` to pick out. Tab on what `n` selected wears the theme, which is the same middle click on the row is. `]d`/`[d` are helix's diagnostic motions, a different binding, and they do still jump to each diagnostic (`docs/lsp.md`) | pardes-specific |
+| `n` / `N` (any pane) | MOTION, not a jump: move the SELECTION to the next / previous look-able text and open NOTHING. Enter — the look chord — on what it leaves selected is what opens it | KEEP, do not touch; not in the corpus (helix's `n`/`N` walk regex search hits). What a step selects is the pane's GRAIN (`output_pane.Grain`, read in `Pardes.lookSpanIn`): in FREE TEXT — a terminal, a file, a PDF, a prose answer buffer — the largest whitespace-delimited run `look.resolve` can act on (`look.lookableSpan`, wrapper punctuation peeled off both ends), several to a line; in a RESULTS BUFFER one stop per ROW, the largest run its head resolves as (`look.lookableLineSpan`), because a row there IS one location and the words after it are the match rather than a second place to go; in a COMMAND list the whole line. The walk is a RING across PANES: every pane that has performed a Look, most recent first (`Pardes.look_src`), then the output buffers that have not, newest first, and only when both are empty the active pane. Exhausting a pane enters the next at its first (forward) / last (backward) span and the end wraps to the start, so `N` is the exact inverse of `n`. What it lands on becomes an EXPLICIT `vsel` with the cursor on its FIRST column, in the pane the walk focuses. ONE motion in every pane kind and every buffer kind — a PDF steps the `+Search` buffer its own search filled, `n` to select the row and Enter to jump. The single thing a buffer may change is that grain, and it changes it by BEING a kind of buffer rather than by a branch: `output_pane.Traits.steps` (a list of locations) makes a step take one row at a time, and `Traits.commands` makes it take the WHOLE LINE, because a command list (`Themes`/`Fonts`) holds words to run and there is no path inside `Theme gruvbox` to pick out. Tab on what `n` selected wears the theme, which is the same middle click on the row is. `]d`/`[d` are helix's diagnostic motions, a different binding, and they do still jump to each diagnostic (`docs/lsp.md`) | pardes-specific |
 | insert: printable text | file: real edit; terminal: typed run splice | | helix-verified (file) |
 | insert: `Enter` | newline; keeps the current full indent levels and adds one 4-space logical tab when the text before the cursor ends in `(`, `[`, `{`, or `)` (including `})`) | plain lines match `insert_newline`; delimiter heuristic is pardes-specific | helix-verified (plain) / pardes-specific (delimiter) |
 | insert: `Backspace` (+ `Shift-Backspace`) | delete prev char, joins lines at col 0; in a line's leading blanks, back to the previous 4-column indent stop (a whole unit when on one; a tab still goes alone) | matches `delete_char_backward` and its dedent; `Ctrl-h` alias in B | helix-verified |
diff --git a/docs/macos.md b/docs/macos.md
index cf7091e6..8bb81be6 100644
--- a/docs/macos.md
+++ b/docs/macos.md
@@ -495,7 +495,7 @@ has none:
 The face is the shell's business and the size is the window's, so the two are
 reached differently on purpose.
 
-`Font <name>` and the `FontSel` picker are ordinary core builtins, enabled by
+`Font <name>` and the `Fonts` picker are ordinary core builtins, enabled by
 `pardes.font_picker` — the frontends that draw their own text, which is now the
 SDL shell and this one. `src/fonts.zig` moved out of `gui/` for that reason. It
 walks the platform's font directories and reads four small sfnt tables per file
diff --git a/docs/themes.md b/docs/themes.md
index 38596819..5349a764 100644
--- a/docs/themes.md
+++ b/docs/themes.md
@@ -3,11 +3,11 @@
 Pardes ships fifteen native palettes: six originals, six classic-inspired
 adaptations and three contrast variants, designed for tags, text, search, diagnostics and embedded
 terminals together. `orchard` is the initial theme.
-Execute `Theme <name>` anywhere, or open `ThemeSel` with `SPC t t` and select
+Execute `Theme <name>` anywhere, or open `Themes` with `SPC t t` and select
 a theme's command. Put the same command in your [startup configuration](config.md)
 to keep a preference. `NextColor` cycles through the native themes first,
 then the retained `helix`, `dark` and `acme` themes and imported palettes.
-`ThemeSel` groups the new palettes under `Pardes themes`, followed by
+`Themes` groups the new palettes under `Pardes themes`, followed by
 `Legacy and imported themes`; its navigation skips the section headings.
 See the [Agave visual review](ui-review.md) for the original six-palette gallery.
 
diff --git a/docs/ui-review.md b/docs/ui-review.md
index 1180a20e..decf042d 100644
--- a/docs/ui-review.md
+++ b/docs/ui-review.md
@@ -12,7 +12,7 @@ and silver-blue chrome. `forge_black` and `orchard_black` use pure black;
 `forge_soft` joins `dusk`, `lagoon` and `solarium` as deliberately softer
 alternatives. Light and Acme-inspired choices remain available.
 
-`ThemeSel` opens with the native collection, followed by a separate legacy
+`Themes` opens with the native collection, followed by a separate legacy
 and imported section. Keyboard navigation skips both section headings.
 
 `Collapse` now transfers all released rows to one expanded pane, preferring
@@ -36,7 +36,7 @@ sent to the user's session.
 
 - [Six contrast studies, OS screenshot crops](screenshots/theme-preferences.png)
 - [Neutral Forge, full workspace](screenshots/theme-preferences-forge.png)
-- [Native-first ThemeSel, full workspace](screenshots/theme-selector.png)
+- [Native-first Themes, full workspace](screenshots/theme-selector.png)
 
 ## Compact rails, classic palettes and workspace pets