lkn
/
kate-deft
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(README): remove 'Why not just use Kate's command bar?' section

This commit is contained in:
Levi Neely 2026-10-08 20:56:47 +02:00
parent d799603587
commit 59e1178958
1 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -43,18 +43,6 @@ These are hard constraints that shape every decision:
> **`M-x` (keyboard), a radial caret menu (mouse), and the `:` command line (optional).** > **`M-x` (keyboard), a radial caret menu (mouse), and the `:` command line (optional).**
> **No action requires an F-key or a chord.** > **No action requires an F-key or a chord.**
## Why not just use Kate's command bar?
Kate's `KCommandBar` is a sealed widget: it accepts a list of actions via
`setActions()` and exposes **no hook** to customize its matcher. Its matcher,
`KFuzzyMatcher`, is single-needle, strictly in-order subsequence, with **no typo
tolerance** — by KDE's own documentation, `"gti"` will not match `"git"`. There
is no "orderless" (space-separated tokens in any order) and no company-style
live completion.
So the project replaces the palette rather than extending it, built on a custom
matcher (`FuzzyRanker`).
## Environment ## Environment
- Kate 25.12.3, KDE Frameworks 6, Qt 6 - Kate 25.12.3, KDE Frameworks 6, Qt 6