mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-22 00:21:43 +01:00
feat(hotkeys): read a whkdrc
komorebi for Windows' users bind komorebic in a whkdrc. `whkd::parse` reads it into the same model as an skhdrc: `keys : command` bindings with the Windows virtual key names whkd takes, per-application lists with `Ignore` and `Default`, `.pause` and `.pause_hook`. A `#` starts a comment wherever it is, as in whkd. whkd requires its sections in a fixed order; the reader takes them in any. `.shell` is noted, since commands run through `sh -c`, side-specific modifiers are approximated, and keys KDE has no key for (the keypad's) are left out with a warning. whkd's own parser, `whkd-parser`, is not used to read: it requires `.shell` to be pwsh, powershell or cmd and panics on anything else, and it matches Windows process names. It is under the same license as komorebi, so it is a dev-dependency at v0.2.10, and a test reads every whkdrc of the corpus and the example of whkd's README with both parsers and requires the same bindings. deny.toml allows its git source. The corpus test now also reads the whkdrc fixtures, and checks that the files of a case read into the same keymap, apart from where each binding was written.
This commit is contained in:
1 parent
ecf91f077f
commit
dc9d12b34a
10 files changed
+881
-11
No files matched your search
+6
-4
@@ -712,10 +712,12 @@ or text that is a number, which is also what the module's typed `config` takes.
|
||||
## Why are the key binding files read by parsers written for komorebi?
|
||||
|
||||
All three formats, skhd's, whkd's and sxhkd's, are read by parsers written by hand in
|
||||
`komorebi-hotkeys`. For whkd there is a Rust parser, `whkd-parser`, under the same license
|
||||
as komorebi, but it requires a `.shell pwsh|powershell|cmd` line, panics in `Shell::from` on
|
||||
any other shell, and its per-application bindings match Windows process names. For skhd and
|
||||
sxhkd the reason is not recorded; this entry needs one.
|
||||
`komorebi-hotkeys`. For whkd there is a Rust parser, `whkd-parser`, but it requires a
|
||||
`.shell pwsh|powershell|cmd` line, panics in `Shell::from` on any other shell, and its
|
||||
per-application bindings match Windows process names. It is under the same license as
|
||||
komorebi, so it stays usable as a dev-dependency: a test reads every whkdrc of the fixture
|
||||
corpus with both parsers and compares the bindings. For skhd and sxhkd the reason is not
|
||||
recorded; this entry needs one.
|
||||
|
||||
What is not plain syntax is expanded while the file is read: skhd's `.define` templates and
|
||||
application groups are replaced where they are used, so the model has only expanded bindings
|
||||
|
||||
Reference in new issue
Block a user