Fork of river (Wayland compositor, https://codeberg.org/river/river)
Go to file
Isaac Freund 2eb013e214
Cursor: implement initial touch support
Still TODO are:
- Touch support for drags
- Mapping input devices to outputs (necessary for good multi-monitor
touch support)

Co-authored-by: Daan Vanoverloop <daan@vanoverloop.xyz>
2022-06-22 11:06:35 +02:00
.builds ci: make wget output non verbose 2022-05-01 19:03:32 +02:00
.github/workflows ci: fix xbps invocation 2022-05-29 20:17:39 +02:00
common code: relicense to GPL-3.0-only 2022-01-31 19:33:22 +01:00
completions Cursor: revive 'always' focus-follows-cursor mode 2022-06-03 12:03:08 +02:00
contrib contrib: add desktop file 2022-01-08 15:37:47 +09:00
deps deps: update to latest zig-wayland 2022-05-11 18:02:32 +02:00
doc Cursor: revive 'always' focus-follows-cursor mode 2022-06-03 12:03:08 +02:00
example example/init: don't use exec 2022-06-17 19:29:28 +02:00
protocol river-status: add mode event to seat status 2022-06-01 00:15:09 +02:00
river Cursor: implement initial touch support 2022-06-22 11:06:35 +02:00
riverctl deps: update to latest zig-wayland 2022-05-11 18:02:32 +02:00
rivertile deps: update to latest zig-wayland 2022-05-11 18:02:32 +02:00
.editorconfig editorconfig: add scdoc config 2020-06-17 16:22:53 +02:00
.gitignore code: update to zig 0.8.0 2021-06-05 17:29:58 +00:00
.gitmodules code: switch to custom wlroots/libwayland bindings 2020-12-13 22:53:33 +01:00
build.zig build: don't scan xdg-output 2022-06-03 23:31:07 +02:00
CONTRIBUTING.md doc: Add additional style rule to CONTRIBUTING.md 2022-03-02 15:34:51 +01:00
LICENSE Relicense to GPL-3.0-or-later 2020-05-02 19:21:10 +02:00
PACKAGING.md docs: add note on example init file to PACKAGING.md 2022-05-22 19:17:14 +02:00
README.md docs: create PACKAGING.md 2022-05-22 15:35:42 +02:00

river

River is a dynamic tiling Wayland compositor with flexible runtime configuration.

Join us at #river on irc.libera.chat. Read our man pages and our 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 rivertile layout generator is provided.
  • Scriptable configuration and control through a custom Wayland protocol and separate riverctl binary implementing it.

Building

Packaging status

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.9
  • wayland
  • wayland-protocols
  • wlroots 0.15
  • xkbcommon
  • libevdev
  • pixman
  • pkg-config
  • scdoc (optional, but required for man page generation)

Then run, for example:

zig build -Drelease-safe --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).