diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-02 20:38:06 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-02 20:38:06 -0500 |
| commit | 13b053c2a99d30c1131d920a62febde6ee9a628b (patch) | |
| tree | 8be336af2b88cf69404f00f361793a598866ee21 /tests | |
| parent | 2377c06a65d38a84c8a29163c01cc386a5047e71 (diff) | |
| download | dotemacs-13b053c2a99d30c1131d920a62febde6ee9a628b.tar.gz dotemacs-13b053c2a99d30c1131d920a62febde6ee9a628b.zip | |
feat(ui): name the operation in completing-read prompts
A picker prompt is the last thing shown before a command commits, so a bare noun leaves a mis-keyed command ambiguous. Hitting C-f8 (project agenda) instead of C-f9 (AI-vterm picker) gave the same "Project:" prompt with no signal which one was about to run.
Reworded 17 prompts across 8 modules so each names the operation rather than just the thing being chosen: "Project:" becomes "Show agenda for project:", "F6:" becomes "Run tests:", the dwim-shell sub-prompts gain their context (checksum algorithm, PDF compression quality, text-to-speech voice, run dwim-shell command), the two contact pickers split into "Find contact:" and "Insert contact email:", and the dirvish ediff, org finalize, and custom-comments length/box-style prompts get the same treatment.
I audited all ~124 completing-read / read-* call sites; the rest already named their operation and were left alone. These are prompt-string changes only, no logic touched.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions