diff options
| author | Ivan Molodetskikh <yalterz@gmail.com> | 2024-11-09 11:00:45 +0300 |
|---|---|---|
| committer | Ivan Molodetskikh <yalterz@gmail.com> | 2024-11-09 11:04:39 +0300 |
| commit | 642c5acebb0824f9d56cacfb51f834d2355436f9 (patch) | |
| tree | 22d1e4b45c179acf254b52a6916dfdcf647f1278 /wiki/Application-Issues.md | |
| parent | 0886dedff1210439f668b3b7c8f040b2d732baa2 (diff) | |
| download | niri-642c5acebb0824f9d56cacfb51f834d2355436f9.tar.gz niri-642c5acebb0824f9d56cacfb51f834d2355436f9.tar.bz2 niri-642c5acebb0824f9d56cacfb51f834d2355436f9.zip | |
wiki: Remove outdated info from Application Issues
Diffstat (limited to 'wiki/Application-Issues.md')
| -rw-r--r-- | wiki/Application-Issues.md | 18 |
1 files changed, 3 insertions, 15 deletions
diff --git a/wiki/Application-Issues.md b/wiki/Application-Issues.md index 82b1088f..1f8dd73e 100644 --- a/wiki/Application-Issues.md +++ b/wiki/Application-Issues.md @@ -1,20 +1,8 @@ ### VSCode -There seems to be a bug in VSCode's Wayland backend until 1.86.0 which causes the window to not show up when using server-side decorations. So, to run VSCode: - -1. Make sure VSCode is 1.86.0 or above, or that `prefer-no-csd` is **not set** in the niri config -2. Run `code --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations` - -Also, if you're having issues with some VSCode hotkeys, try starting `Xwayland` and setting the `DISPLAY=:0` environment variable for VSCode. That is, still running VSCode with the Wayland backend, but with `DISPLAY` set to a running Xwayland instance. Apparently, VSCode currently unconditionally queries the X server for a keymap. - -### Chromium - -When creating new windows within Chromium (e.g. with <kbd>Ctrl</kbd><kbd>N</kbd>), there's a Chromium bug with sizing: - -- With CSD (`prefer-no-csd` unset), the window will be a bit smaller than needed -- With SSD (`prefer-no-csd` set), the window buffer will be offset to the top-left - -Both of these can be fixed by resizing the new Chromium window. +If you're having issues with some VSCode hotkeys, try starting `Xwayland` and setting the `DISPLAY=:0` environment variable for VSCode. +That is, still running VSCode with the Wayland backend, but with `DISPLAY` set to a running Xwayland instance. +Apparently, VSCode currently unconditionally queries the X server for a keymap. ### WezTerm |