diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-28 01:11:22 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-28 01:11:22 -0500 |
| commit | b34909973bcf9f0fed940cab5e3192e54708ad7f (patch) | |
| tree | c5a8714fbd7e22d41e4e88199b08140c2bcc5df0 /docs | |
| parent | b75e6ecc1eb0bc16ffd7f8ca6c8a42229419c8d6 (diff) | |
| download | pearl-b34909973bcf9f0fed940cab5e3192e54708ad7f.tar.gz pearl-b34909973bcf9f0fed940cab5e3192e54708ad7f.zip | |
feat(saved): add pearl-delete-saved-query and a sentinel cancel for run
`pearl-saved-queries' was write-only from a user's perspective. Save was bound to the builder, run was bound to a key, but removing a stale entry meant `M-x customize-variable RET pearl-saved-queries RET` and a manual delete from the Customize buffer. `pearl-delete-saved-query` under `C-; L k q` (and `q` in the transient's Delete group) closes that gap: completes over the saved query names with `[ None. ]` at the top as a cancel, confirms, removes the entry, and persists via `customize-save-variable`. Linear is untouched. Saved queries are local. Pushing them up to Linear as custom views is a separate spec.
While in the same path, `pearl-run-saved-query` got the same sentinel cancel. Both prompts use the keep-order completion table so `[ None. ]` stays at the top regardless of the user's completion sorter. Both error cleanly when `pearl-saved-queries` is empty rather than offering an empty picker. Six tests cover the new command (delete-on-yes, no-at-confirm, sentinel-cancels, unknown-name-errors, empty-list-errors) plus run's sentinel cancel.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions
