docs(niri): match key names case-insensitively in the conflict check
niri accepts lowercase and mixed-case key names such as mod+shift+m, so the grep in the conflict check must ignore case too. strings comes from binutils, which is now said in the docs. Refs #45
This commit is contained in:
+4
-3
@@ -70,11 +70,12 @@ toggle bind will match:
|
||||
|
||||
```bash
|
||||
KEY_RE='(Mod|Super)\+Shift\+M([[:space:]{]|$)' # the key you want to check
|
||||
grep -rnE --include='*.kdl' "$KEY_RE" ~/.config/niri/
|
||||
strings "$(command -v niri)" | grep -E "^[[:space:]]*(//[[:space:]]*)?$KEY_RE"
|
||||
grep -rniE --include='*.kdl' "$KEY_RE" ~/.config/niri/
|
||||
strings "$(command -v niri)" | grep -iE "^[[:space:]]*(//[[:space:]]*)?$KEY_RE"
|
||||
```
|
||||
|
||||
The first command searches your config. `~/.config/niri/` holds
|
||||
Matching ignores case, because niri also accepts `mod+shift+m`. `strings`
|
||||
comes from binutils. The first command searches your config. `~/.config/niri/` holds
|
||||
`config.kdl` and the DMS-managed `dms/binds.kdl`, which `config.kdl`
|
||||
includes. `--include='*.kdl'` skips the `binds.kdl.pre-*` backups. If you
|
||||
include files from elsewhere, add their paths. The second command searches
|
||||
|
||||
Reference in New Issue
Block a user