aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2025-08-27 14:20:22 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2025-08-29 09:35:01 +0300
commit2bb26f0281167982d96965cac3b0b5ee10a00d0a (patch)
tree5c587717a0ba2afe26a80e8c0077af78d11bfab8 /docs
parente11c35c3879ddf5002f17ea836456f01d5d3c4b1 (diff)
downloadniri-2bb26f0281167982d96965cac3b0b5ee10a00d0a.tar.gz
niri-2bb26f0281167982d96965cac3b0b5ee10a00d0a.tar.bz2
niri-2bb26f0281167982d96965cac3b0b5ee10a00d0a.zip
wiki/Packaging-niri: Mention shell completions
Diffstat (limited to 'docs')
-rw-r--r--docs/wiki/Packaging-niri.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/wiki/Packaging-niri.md b/docs/wiki/Packaging-niri.md
index fdf2b545..ea809abf 100644
--- a/docs/wiki/Packaging-niri.md
+++ b/docs/wiki/Packaging-niri.md
@@ -123,3 +123,8 @@ It contains the exact dependency versions that I used when testing the release.
If you need to change the versions of some dependencies, pay extra attention to `smithay` and `smithay-drm-extras` commit hash.
These crates don't currently have regular stable releases, so niri uses git snapshots.
Upstream frequently has breaking changes (API and behavior), so you're strongly advised to use the exact commit hash from the niri release's `Cargo.lock`.
+
+### Shell completions
+
+You can generate shell completions for several shells via `niri completions <SHELL>`, i.e. `niri completions bash`.
+See `niri completions -h` for a full list.