60b06a6741
Currently we update output-management clients based on changes in the wlr_output_layout struct. However, this is obviously wrong on closer inspection due to the fact that not all outputs are tracked by the wlr_output_layout at all times. I think this aproach was originally cargo-culted from some other output-management implementation and it needs to go. Luckily, the solution is quite simple since the only way to configure outputs using river is through the wlr-output-management protocol. This means we need to send a new configuration to the output-management client in 3 cases: 1. An output is created 2. An output is destroyed 3. A wlr-output-management config from a client is applied |
||
|---|---|---|
| .builds | ||
| common | ||
| completions | ||
| contrib | ||
| deps | ||
| doc | ||
| example | ||
| protocol | ||
| river | ||
| riverctl | ||
| rivertile | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| build.zig | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| PACKAGING.md | ||
| README.md | ||
river
River is a dynamic tiling Wayland compositor with flexible runtime configuration.
Install from your package manager — Join us at #river on irc.libera.chat — Read our man pages and wiki
Note: river is currently early in development. Expect breaking changes and missing features. Bugs should however be rare at this point, if you run into one don't hesitate to open an issue
Design goals
- Simple and predictable behavior, river should be easy to use and have a low cognitive load.
- Window management based on a stack of views and tags.
- Dynamic layouts generated by external, user-written executables. A default
rivertilelayout generator is provided. - Scriptable configuration and control through a custom Wayland protocol and
separate
riverctlbinary implementing it.
Building
On cloning the repository, you must init and update the submodules as well with e.g.
git submodule update --init
To compile river first ensure that you have the following dependencies installed. The "development" versions are required if applicable to your distribution.
- zig 0.11
- wayland
- wayland-protocols
- wlroots 0.17.1
- xkbcommon
- libevdev
- pixman
- pkg-config
- scdoc (optional, but required for man page generation)
Then run, for example:
zig build -Doptimize=ReleaseSafe --prefix ~/.local install
To enable experimental Xwayland support pass the -Dxwayland option as well.
If you are packaging river for distribution, see also PACKAGING.md.
Usage
River can either be run nested in an X11/Wayland session or directly
from a tty using KMS/DRM. Simply run the river command.
On startup river will run an executable file at $XDG_CONFIG_HOME/river/init
if such an executable exists. If $XDG_CONFIG_HOME is not set,
~/.config/river/init will be used instead.
Usually this executable is a shell script invoking riverctl(1) to create mappings, start programs such as a layout generator or status bar, and perform other configuration.
An example init script with sane defaults is provided here in the example directory.
For complete documentation see the river(1), riverctl(1), and
rivertile(1) man pages.
Licensing
River is released under the GNU General Public License v3.0 only.
The protocols in the protocol directory are released under various licenses by
various parties. You should refer to the copyright block of each protocol for
the licensing information. The protocols prefixed with river and developed by
this project are released under the ISC license (as stated in their copyright
blocks).