Frank
02883d3ed2
Copy of the legacy ~/.pi/agent/docs tree rebuilt as the command-center knowledge base: concept files promoted to path identity, index listings stripped of frontmatter, all wikilinks/relative links resolved, every checkable claim verified against the live fleet (Dankserver = Ryzen 7 7700X + RTX 3090; Strix Halo is Dankclaw), unverifiable claims tagged. kb-lint exits 0.
981 B
981 B
type, title, description, tags, verified
| type | title | description | tags | verified | |||
|---|---|---|---|---|---|---|---|
| howto | Niri Tips and Gotchas | Practical tips for working with niri — Mod key behavior, shell expansion, config reload, vim keys, and programmatic invocation. |
|
2026-08-28 |
Helpful Tips
1. Mod key
Use Mod instead of Super for configs that work both on TTY and in nested windows.
2. No shell expansion in spawn
spawn does not expand $VAR or ~. Use spawn-sh or wrap in sh -c.
3. Config reload
niri supports live-reloading config without restart.
4. Alternative navigation
Vim-like keys (H/J/K/L) are bound by default alongside arrow keys.
5. Programmatic invocation
Every action can be invoked via niri msg action <action-name>.
6. Find XKB keys
Use wev to discover key names.
Related
- Key Bindings Syntax — Configuration details
- Action Reference — All available actions