andrei/niri
1
0
Fork 0
mirror of https://github.com/niri-wm/niri.git synced 2026-06-23 02:05:33 +07:00
Code Issues Packages Projects Releases 10 Wiki Activity

wiki: Improve Layout

Browse Source
This commit is contained in:
Ivan Molodetskikh
2024-03-28 17:50:34 +04:00
parent 4f421907cd
commit 470d65a060
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/Configuration:-Layout.md
+11 -4
View File
@@ -1,6 +1,6 @@
### Overview ### Overview
In the `layout {}` section you can change various settings that influence how the windows are positioned and sized. In the `layout {}` section you can change various settings that influence how windows are positioned and sized.
Here are the contents of this section at a glance: Here are the contents of this section at a glance:
@@ -91,6 +91,13 @@ layout {
} }
``` ```
> [!NOTE]
> Currently, due to an oversight, a preset `fixed` width does not take borders into account.
> I.e., preset `fixed 1000` with 4-wide borders will make the window 992 logical pixels wide.
> This may eventually be corrected.
>
> All other ways of using `fixed` (i.e. `default-column-width` or `set-column-width`) do take borders into account and give you the exact window width that you request.
### `default-column-width` ### `default-column-width`
Set the default width of the new windows. Set the default width of the new windows.
@@ -116,7 +123,7 @@ layout {
> [!NOTE] > [!NOTE]
> `default-column-width {}` causes niri to send a (0, H) size in the initial configure request. > `default-column-width {}` causes niri to send a (0, H) size in the initial configure request.
> >
> This is a bit unclearly defined in the Wayland protocol, so some clients may misinterpret it. > This is a bit [unclearly defined](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/155) in the Wayland protocol, so some clients may misinterpret it.
> In practice, the only problematic client I saw is [foot](https://codeberg.org/dnkl/foot/), which takes this as a request to have a literal zero width. > In practice, the only problematic client I saw is [foot](https://codeberg.org/dnkl/foot/), which takes this as a request to have a literal zero width.
> >
> Either way, `default-column-width {}` is most useful for specific windows, in form of a [window rule](https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules) with the same syntax. > Either way, `default-column-width {}` is most useful for specific windows, in form of a [window rule](https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules) with the same syntax.
@@ -138,9 +145,9 @@ The difference is that the focus ring is drawn only around the active window, wh
> This is because windows using client-side decorations can have an arbitrary shape. > 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 of the config.
> Then, niri will draw focus rings and borders *around* windows that agree to omit their client-side decorations. > Niri will draw focus rings and borders *around* windows that agree to omit their client-side decorations.
> >
> Alternatively, you can override this with the `draw-border-with-background` [window rule](https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules). > Alternatively, you can override this behavior with the `draw-border-with-background` [window rule](https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules).
Focus ring and border have the following options. Focus ring and border have the following options.