Some programs have difficulties with foot as TERM (e. g. aerc’s
terminal). Therefore, it is manually set to xterm-256color and true
colour support is forced in tmux.
Swaync is in stable, mumble 1.4 is in stable and has pulseaudio enabled
by default, the tray target is defined in home-manager upstream and
nix-direnv comes with flake support by default.
The full sysfs is required for steam to discover controllers. Despite
some individual games detecting them, for full controller support
(especially in wine/proton), steam has to detect them.
This requires the key database at ~/.config/aacs/KEYDB.cfg (note the
case, I missed this at first). A guide for how to prepare it can be
found on the Arch Wiki: https://wiki.archlinux.org/title/Blu-ray
This removes ravu-zoom and ravu-lite in favour of standard ravu. It also
adds more nnedi3 shaders with neurons between 2^4 and 2^8, each with a
window size of 8x4. This should give a wide range of options that work
on all machines and still give acceptable results (at least balanced to
the performance).
The reason for this switch is ravu’s subpar performance, since it often
produces more artifacts than it avoids.
It also avoids some code duplication at the cost of making it more
complex.
This configures the home profile for kanshi for an Acer B277K monitor.
Since it is both larger than my previous monitor and has a higher
resolution, a few things change with this.
For one, my preferred setup is now to just have one monitor instead of
having my laptop screen as a secondary display device. Therefore, logind
should not suspend if the lid is closed. Since it fails to accurately
detect when a dock is connected, it is configured to never suspend on
lid switch when external power is connected.
Another thing is that the high resolution makes it necessary to use a
scaling factor, which is quite easy to configure with sway and kanshi.
It does, however, not work for Xwayland clients (they render at a lower
resolution and are scaled up with nearest-neighbor interpolation).
That requires me to no longer force the qt backend to xcb for
qutebrowser, because that significantly lowers the browsing experience.
The setup for sayuri is still to be done.
Simon Bruder