Fork of river (Wayland compositor, https://codeberg.org/river/river)
Go to file
2020-12-12 16:35:33 +01:00
.github/workflows ci: check fmt of build.zig 2020-12-05 22:54:53 +01:00
contrib control: implement set-repeat 2020-11-18 15:28:33 +01:00
deps keyboard: handle destruction 2020-11-29 21:05:27 +01:00
doc focus-follow-cursor: Change output focus when needed 2020-12-07 13:51:06 +01:00
example meta: make copyright headers more maintainable 2020-11-11 20:33:43 +01:00
include code: Remove most of the hack around @cImport and flexible arrays 2020-10-30 15:23:52 +01:00
protocol meta: make copyright headers more maintainable 2020-11-11 20:33:43 +01:00
river render: remove unnecessary call to wlr_output_effective_resolution 2020-12-12 16:35:33 +01:00
riverctl meta: make copyright headers more maintainable 2020-11-11 20:33:43 +01:00
rivertile meta: make copyright headers more maintainable 2020-11-11 20:33:43 +01:00
.editorconfig editorconfig: add scdoc config 2020-06-17 16:22:53 +02:00
.gitignore docs: small man pages fixes and updates 2020-06-17 12:14:23 +02:00
.gitmodules Add submodule 2020-11-01 13:58:54 +01:00
AUTHORS meta: make copyright headers more maintainable 2020-11-11 20:33:43 +01:00
build.zig screencopy: add workaround for wlroots bug 2020-12-05 01:10:06 +01:00
CONTRIBUTING.md docs: Advertise irc channel instead of the old matrix channel 2020-11-01 10:31:08 +01:00
LICENSE Relicense to GPL-3.0-or-later 2020-05-02 19:21:10 +02:00
README.md code: use zig 0.7.0 and wlroots 0.12.0 2020-11-10 11:46:03 +01:00

river

river is a dynamic tiling wayland compositor that takes inspiration from dwm and bspwm.

Note: river is currently early in development. Expect breaking changes and missing features. If you run into a bug don't hesitate to open an issue

Design goals

  • Simplicity and minimalism, river should not overstep the bounds of a window manager.
  • Window management based on a stack of views and tags.
  • Dynamic layouts generated by external, user-written executables. (A default rivertile layout generator is provided.)
  • Scriptable configuration and control through a custom wayland protocol and separate riverctl binary 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:

  • zig 0.7.0
  • wayland
  • wayland-protocols
  • wlroots 0.12.0
  • xkbcommon
  • libevdev
  • pixman
  • pkg-config
  • scdoc (optional, but required for man page generation)

Note: NixOS users may refer to the Building on NixOS wiki page

Then run, for example,

zig build -Drelease-safe=true --prefix /usr/local install

to build and install the binaries and man pages to /usr/local/bin and /usr/local/share/man. To enable experimental Xwayland support pass the -Dxwayland=true option as well.

Usage

River can either be run nested in an X11/wayland session or directly from a tty using KMS/DRM.

River has no keybindings by default; mappings can be created using the map command of riverctl. Generally, creating mappings and other configuration is done with a shell script. River will execute any arbitrary shell command passed with the -c flag during startup. For example:

river -c /path/to/config.sh

An example script with sane defaults is provided here in the contrib directory.

For a complete list of commands see the riverctl(1) man page.

Keyboard configuration is not yet implemented in river, but since river uses libxkbcommon you may use the following environment variables to set defaults:

  • XKB_DEFAULT_RULES
  • XKB_DEFAULT_MODEL
  • XKB_DEFAULT_LAYOUT
  • XKB_DEFAULT_VARIANT
  • XKB_DEFAULT_OPTIONS

Possible values for these variables can be found in the xkeyboard-config(7) man page. For example, to use a dvorak layout one could start river with

XKB_DEFAULT_LAYOUT="us(dvorak)" river

Development

Check out the roadmap if you'd like to see what has been done and what is left to do.

If you are interested in the development of river, please join us at #river on freenode. You should also read CONTRIBUTING.md if you intend to submit patches.

Licensing

river is released under the GNU General Public License version 3, or (at your option) any later version.

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).