|Repos Using This
|Packages Using This
|Most Recent Commit
|4 days ago
|KDE Plasma add-on, that tiles your windows automatically and lets you manage them via keyboard, similarly to i3, Sway or dwm.
|3 months ago
|dwm for Wayland
|4 months ago
|A curated list of Wayland code and resources.
|8 years ago
|Modular Wayland compositor
|a month ago
|Cagebreak: A Wayland Tiling Compositor Inspired by Ratpoison
|2 years ago
|taiwins, a modern wayland compositor
|7 years ago
|June 10, 2017
|Dynamic window manager with support for Wayland
|a month ago
|A wlroots and dwl based tiling wayland compositor based around creating layouts
|2 days ago
|miracle-wm is a tiling Wayland compositor based on Mir
|9 years ago
|Windowmanager for wayland
Migrated to Codeberg
This project has migrated to Codeberg.
dwl is a compact, hackable compositor for Wayland based on wlroots. It is intended to fill the same space in the Wayland world that dwm does in X11, primarily in terms of philosophy, and secondarily in terms of functionality. Like dwm, dwl is:
dwl is not meant to provide every feature under the sun. Instead, like dwm, it sticks to features which are necessary, simple, and straightforward to implement given the base on which it is built. Implemented default features are:
Features under consideration (possibly as patches) are:
Feature non-goals for the main codebase include:
dwl has the following dependencies:
wlroots (compiled with the libinput backend)
wayland-protocols (compile-time only)
pkg-config (compile-time only)
If you enable X11 support:
wlroots (compiled with X11 support)
Xwayland (runtime only)
Simply install these (and their
-devel versions if your distro has separate
development packages) and run
make. If you wish to build against a Git
version of wlroots, check out the wlroots-next branch.
To enable XWayland, you should uncomment its flags in
All configuration is done by editing
config.h and recompiling, in the same
manner as dwm. There is no way to separately restart the window manager in
Wayland without restarting the entire display server, so any changes will take
effect the next time dwl is executed.
As in the dwm community, we encourage users to share patches they have created. Check out the patches page on our wiki!
dwl can be run on any of the backends supported by wlroots. This means you can
run it as a separate window inside either an X11 or Wayland session, as well
as directly from a VT console. Depending on your distro's setup, you may need
to add your user to the
input groups before you can run dwl on
a VT. If you are using
systemd-logind you need to install
polkit; otherwise you need to add yourself in the
seat group and
enable/start the seatd daemon.
When dwl is run with no arguments, it will launch the server and begin handling
any shortcuts configured in
config.h. There is no status bar or other
decoration initially; these are instead clients that can be run within
the Wayland session.
Do note that the background color is black.
If you would like to run a script or command automatically at startup, you can
specify the command using the
-s option. This command will be executed as a
shell command using
/bin/sh -c. It serves a similar function to
but differs in that the display server will not shut down when this process
terminates. Instead, dwl will send this process a SIGTERM at shutdown and wait
for it to terminate (if it hasn't already). This makes it ideal for execing into
a user service manager like s6, anopa, runit, or
-s command is run as a child process of dwl, which means that it
does not have the ability to affect the environment of dwl or of any processes
that it spawns. If you need to set environment variables that affect the entire
dwl session, these must be set prior to running dwl. For example, Wayland
requires a valid
XDG_RUNTIME_DIR, which is usually set up by a session manager
systemd-logind. If your system doesn't do this
automatically, you will need to configure it prior to launching
export XDG_RUNTIME_DIR=/tmp/xdg-runtime-$(id -u)
mkdir -p $XDG_RUNTIME_DIR
Information about selected layouts, current window title, app-id, and
selected/occupied/urgent tags is written to the stdin of the
-s command (see
printstatus() function for details). This information can be used to
populate an external status bar with a script that parses the information.
Failing to read this information will cause dwl to block, so if you do want to
run a startup command that does not consume the status information, you can
close standard input with the
<&- shell redirection, for example:
dwl -s 'foot --server <&-'
If your startup command is a shell script, you can achieve the same inside the script with the line
To get a list of status bars that work with dwl consult our wiki.
You can find a list of useful resources on our wiki.
dwl began by extending the TinyWL example provided (CC0) by the sway/wlroots developers. This was made possible in many cases by looking at how sway accomplished something, then trying to do the same in as suckless a way as possible.
Many thanks to suckless.org and the dwm developers and community for the inspiration, and to the various contributors to the project, including: