wiki: Improvements

This commit is contained in:
Ivan Molodetskikh
2024-03-28 21:07:48 +04:00
parent c9a47f8283
commit f46e937949
2 changed files with 11 additions and 9 deletions
+1 -1
View File
@@ -144,7 +144,7 @@ The difference is that the focus ring is drawn only around the active window, wh
> That is, they will show up through semitransparent windows.
> This is because windows using client-side decorations can have an arbitrary shape.
>
> If you don't like that, you should uncomment the `prefer-no-csd` setting at the top level of the config.
> If you don't like that, you should uncomment the `prefer-no-csd` setting at the [top level](./Configuration:-Miscellaneous.md) of the config.
> Niri will draw focus rings and borders *around* windows that agree to omit their client-side decorations.
>
> Alternatively, you can override this behavior with the `draw-border-with-background` [window rule](https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules).
+10 -8
View File
@@ -29,20 +29,20 @@ hotkey-overlay {
### `spawn-at-startup`
Add lines like this to spawn processes at startup.
Add lines like this to spawn processes at niri startup.
`spawn-at-startup` accepts a path to the program binary as the first argument, followed by arguments to the program.
This option works the same way as the `spawn` key binding action, so please read about all the subtleties on the [key bindings](./Configuration:-Key-Bindings.md) page.
Note that running niri as a systemd session supports xdg-desktop-autostart out of the box, which may be more convenient to use.
Thanks to this, apps that you configured to autostart in GNOME will also "just work" in niri, without any manual `spawn-at-startup` configuration.
This option works the same way as the `spawn` key binding action, so please read about all its subtleties on the [key bindings](./Configuration:-Key-Bindings.md) page.
```
spawn-at-startup "waybar"
spawn-at-startup "alacritty"
```
Note that running niri as a systemd session supports xdg-desktop-autostart out of the box, which may be more convenient to use.
Thanks to this, apps that you configured to autostart in GNOME will also "just work" in niri, without any manual `spawn-at-startup` configuration.
### `prefer-no-csd`
This flag will make niri ask the applications to omit their client-side decorations.
@@ -50,11 +50,13 @@ This flag will make niri ask the applications to omit their client-side decorati
If an application will specifically ask for CSD, the request will be honored.
Additionally, clients will be informed that they are tiled, removing some rounded corners.
With `prefer-no-csd` set, applications that negotiate server-side decorations through the xdg-decoration protocol will have focus ring and border drawn around them without a solid colored background.
With `prefer-no-csd` set, applications that negotiate server-side decorations through the xdg-decoration protocol will have focus ring and border drawn around them *without* a solid colored background.
> [!NOTE]
> Unlike most other options, `prefer-no-csd` currently only affects applications started *after* the config was saved.
> Unlike most other options, changing `prefer-no-csd` will not affect already running applications.
> This mainly has to do with niri working around a [bug in SDL2](https://github.com/libsdl-org/SDL/issues/8173) that prevents SDL2 applications from starting.
>
> Restart applications after changing `prefer-no-csd` in the config to apply it.
```
prefer-no-csd
@@ -73,7 +75,7 @@ Niri will create the last folder of the path if it doesn't exist.
screenshot-path "~/Pictures/Screenshots/Screenshot from %Y-%m-%d %H-%M-%S.png"
```
You can also set it to `null` to disable saving screenshots to disk.
You can also set this option to `null` to disable saving screenshots to disk.
```
screenshot-path null