(3686dd6) Open a command prompt on the board with : and parse what is typed, and bump to 0.32.15

The board reads. Changing anything meant quitting it and retyping an id
that was already selected. So `:` opens a one line editor in the footer
and the line is a worklane command, spelled exactly as the shell spells
it.

This is the mode and the grammar check, not the doing. Enter tokenises
the line with split_line, prepends the binary's own name and hands the
arguments to the same Cli definition the shell reaches, so a flag added
to a command is typeable here the day it is added and no list of verbs
lives on the board to go stale. A line that resolves is named and the
prompt closes; a line that does not keeps the prompt open with the line
intact and clap's own message, cut back to what fits a row. Running it
is 53ffb94, and the notice and the `↵ check` key both say so rather than
reading like a move that happened.

The prompt owns the keyboard while it is open, the contract search_key
and picker_key already keep, and declines ctrl-c for the same reason
they do. A line that ends inside a quote never reaches clap, which is
what the splitter's Unclosed state is for. --help is caught, or clap's
page lands on the alternate screen the way an unsunk println! would.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ansho Rei
2026-08-27 21:07:26 +02:00
co-authored by Claude Opus 5
parent bf7d8e05d8
commit f16e2aba0c
5 changed files with 853 additions and 5 deletions
+17 -2
View File
@@ -8,8 +8,9 @@ mod completions;
mod handlers;
mod history;
mod install;
/// Nothing in the binary splits a line yet: the prompt that will is 3686dd6, and the
/// allow goes when it lands. The tests are what drive it in the meantime.
/// The command prompt reads `split_line` and `unclosed`; `cursor_arg` and `at_new_arg` are
/// what completing an argument needs and nothing reads them yet, so the allow stays until
/// 00a14e7 and 952a9f8 land. The tests are what drive them in the meantime.
#[cfg_attr(not(test), allow(dead_code))]
mod split;
mod tag;
@@ -219,6 +220,14 @@ fn run_tui(paths: &[std::path::PathBuf], start: &std::path::Path) -> Result<()>
continue;
}
// And the command prompt, third, on the same contract: while a command is being
// typed `q` is a letter, `d` leaves the columns alone and `tab` stays out of the
// project tabs. No screen, because nothing it does measures the board yet. The
// rule is `Board::prompt_key`, where a test can reach it.
if board.prompt_key(key) {
continue;
}
match key.code {
// One arm, because the two keys mean one thing: close what is open, and
// quit when there is nothing left to close. Two arms carrying one rule
@@ -262,6 +271,12 @@ fn run_tui(paths: &[std::path::PathBuf], start: &std::path::Path) -> Result<()>
// at an open picker is taken by `picker_key` to open the picker's own
// query, so this arm is only ever the way in to the board's prompt.
KeyCode::Char('/') => board.open_search(),
// The way in to the command prompt, and the same single-shot arm `/` is:
// from the next keypress on, `prompt_key` above has the keyboard. A `:`
// typed into either open prompt is a character there and one pressed at an
// open picker is swallowed by it, so this arm is only ever the way in from
// the board itself. Free of every existing binding.
KeyCode::Char(':') => board.open_prompt(),
// `y` as in yank, for the readers this board is for, and the only letter
// left that a vim hand would reach for. The clipboard is handed in rather
// than reached for inside `Board`, so the suite can drive both answers.