Zander671/river
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Fork of river (Wayland compositor, https://codeberg.org/river/river)
393 Commits 1 Branch 0 Tags 3.6 MiB
Zig 92.7%
Shell 3.8%
C 2.7%
Python 0.8%
0c4e3295b1
Go to file
Isaac Freund 0c4e3295b1
cursor: implement implicit grabs 
When a button is held down and the cursor leaves a surface, events now
continue to be sent to the client. This allows e.g. dragging a scroll
bar from outside the surface.
2020-08-07 13:54:58 +02:00
.github/workflows ci: use void linux 2020-07-18 01:28:41 +02:00
contrib Implement csd-filter-add and float-filter-add commands 2020-07-16 21:24:08 +02:00
doc doc: shorten riverctl’s synopsis 2020-08-01 12:36:52 +02:00
example river-status: simplify example client 2020-06-06 15:07:07 +02:00
include Clean up some memory leaks 2020-06-02 13:45:56 +02:00
protocol meta: update layer shell xml 2020-07-28 12:32:56 +02:00
river cursor: implement implicit grabs 2020-08-07 13:54:58 +02:00
riverctl code: improve error handling consistency 2020-06-26 00:59:31 +02:00
rivertile rivertile: fix underflow if views < masters 2020-06-19 13:53:20 +02: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
build.zig code: handle out of memory as well as possible 2020-07-05 22:49:17 +02:00
CONTRIBUTING.md docs: update commit style guidelines 2020-06-05 00:59:12 +02:00
LICENSE Relicense to GPL-3.0-or-later 2020-05-02 19:21:10 +02:00
README.md code: update to wlroots 0.11.0 2020-07-16 21:20:43 +02:00

README.md

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

To compile river first ensure that you have the following dependencies installed:

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

Note: NixOS users should 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).