aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlanastara <12953847+lanastara@users.noreply.github.com>2025-02-27 20:16:27 +0100
committerGitHub <noreply@github.com>2025-02-27 19:16:27 +0000
commit311f3be5d861bfb12ee8b3d7241bd1d1fcb5110b (patch)
tree7d41ccf28360353eb659ece9e4ac29f0366559d4
parent70dcd229cfaa54946163ccf0a1ea0ce595a35cc4 (diff)
downloadniri-311f3be5d861bfb12ee8b3d7241bd1d1fcb5110b.tar.gz
niri-311f3be5d861bfb12ee8b3d7241bd1d1fcb5110b.tar.bz2
niri-311f3be5d861bfb12ee8b3d7241bd1d1fcb5110b.zip
wiki: remove wezterm issues (#1182)
* wiki: added note about nightly wezterm * Update wiki/Application-Issues.md --------- Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>
-rw-r--r--wiki/Application-Issues.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/wiki/Application-Issues.md b/wiki/Application-Issues.md
index 80993a72..34861876 100644
--- a/wiki/Application-Issues.md
+++ b/wiki/Application-Issues.md
@@ -6,6 +6,9 @@ Apparently, VSCode currently unconditionally queries the X server for a keymap.
### WezTerm
+> [!NOTE]
+> Both of these issues seem to be fixed in the nightly build of WezTerm.
+
There's [a bug](https://github.com/wez/wezterm/issues/4708) in WezTerm that it waits for a zero-sized Wayland configure event, so its window never shows up in niri. To work around it, put this window rule in the niri config (included in the default config):
```kdl