dwm (dynamic window manager) is a lightweight tiling window manager for the X Window System built around minimalism, performance, and source-code customization. If you're tired of resource-heavy desktop environments stealing your CPU cycles, dwm strips away the bloat. It leaves you with a fast, keyboard-driven workspace that gets out of your way.
Most graphical interfaces force your hand with complex menus, floating windows, and hidden settings panels. dwm takes a different path. It manages windows in tiled, monocle, and floating layouts, organizing your screen automatically so you don't spend time dragging pixels. Configuration doesn't happen through a graphical settings menu. Instead, you modify a C header file and recompile the source code. That sounds intimidating, but the entire codebase is famously kept under two thousand lines of code.
Understanding the dwm Philosophy
The project comes from the suckless.org community, a group known for software that adheres to simplicity, clarity, and frugality. They believe that code should be small enough to understand completely. You won't find bloated configuration frameworks or background daemons running telemetry. Every line of code exists for a clear reason.
Using dwm changes how you interact with your computer. You rely heavily on keyboard shortcuts rather than a mouse. Windows tile automatically as you open them, splitting your monitor space efficiently. If you open a terminal, it takes half the screen. Open another, and they split again. This layout engine adapts dynamically to whatever workflow you're running, whether that's coding, writing, or monitoring system logs.
Installing and Setting Up dwm
Getting started requires a working Linux installation running Xorg. Most major Linux distributions include dwm in their official package repositories or community package managers like the Arch User Repository (AUR).
To install it on an Arch-based system, you can run:
sudo pacman -S dwm
If you prefer building from source to customize it right away, you clone the official repository via git:
git clone https://git.suckless.org/dwm
cd dwm
sudo make clean install
Building from source requires development tools and Xlib header files. On Debian-based systems, you'll need packages like build-essential and libx11-dev installed before compiling. Once installed, you can launch dwm from your display manager (like LightDM or GDM) or start it manually using a .xinitrc file with the command exec dwm.
Customization Through Source Code
Unlike mainstream desktop environments that provide point-and-click settings panels, dwm keeps its configuration inside a file named config.h. When you first download the source code, this file doesn't exist yet. You generate it by copying a template:
cp config.def.h config.h
Opening config.h reveals plain C arrays mapping keyboard shortcuts to window management functions. Want to change the modifier key from the Alt key to the Super (Windows) key? You change Mod1Mask to Mod4Mask. Want to change your default terminal application from st to alacritty? You update the termcmd definition right inside the file.
/* example snippet from config.h */
static const char *termcmd[] = { "alacritty", NULL };
After making any change to config.h, you apply it by recompiling and restarting:
sudo make clean install
You don't even need to restart your X session. dwm supports a hot-key combination (typically Mod+Shift+Q or Mod+Shift+R depending on your setup) that restarts the window manager in place without closing your running applications.
Enhancing Functionality With Patches
Because dwm aims for extreme minimalism, it leaves out features that many users consider standard, such as window borders, gaps, or system trays. Instead of bloating the core program, the developers created a patch system.
Patches are small code modifications contributed by the community. To add a feature like useless gaps or status bar colors, you download a .diff file matching your exact version of dwm and apply it to your source tree:
patch -p1 < dwm-gaps-20200510.diff
Common patches include:
- Vanity Gaps: Adds adjustable spacing between tiled windows.
- Systray: Embeds system tray icons into the top status bar.
- Pertag: Remembers individual layouts and tags for different workspaces.
- FMS (Full Moon Status): Extends status monitoring for battery and network stats.
If a patch conflicts with another, you'll have to resolve the hunk rejections manually in a text editor. This teaches you how the underlying C code operates, turning you from a passive consumer into an active maintainer of your own software stack.
Daily Workflow and Navigation
Mastering dwm takes a few days of muscle memory adaptation. The top bar displays your tags (workspaces), the layout indicator, and the title of the currently focused window.
- Tags: Instead of traditional virtual desktops, dwm uses tags. A window can inhabit multiple tags simultaneously, and you can view multiple tags at once.
- Layouts: Cycling through layouts happens instantly via key chords. You can switch from a tiling grid to a monocle view (where every window takes up the full screen) with a quick keystroke.
- Focus Management: Moving between windows uses directional keys combined with your modifier key, keeping your hands anchored on the home row.
Common default keybindings include:
Mod + Shift + Enter: Open terminal.Mod + j / k: Focus next or previous window.Mod + Space: Cycle through available layouts.Mod + Shift + C: Close focused window.
Frequently Asked Questions
Do I need to know C programming to use dwm?
You don't need to write C code from scratch, but you do need basic familiarity to read config.h and troubleshoot patch compilation errors. Knowing how to change variable values inside a C struct is usually enough for daily configuration.
How do I check battery life or volume without a desktop environment?
Users typically run lightweight status bar generators like slstatus (also from suckless) or polybar. These programs write system information directly to the root window title or status bar text field every few seconds.
Can I run graphical applications like web browsers?
Yes. dwm manages any standard X11 application. Web browsers like Firefox or Chromium run smoothly, respect tiling layouts, and can easily be toggled into floating mode when you need custom window dimensions.
What happens if a patch fails to apply?
If a patch fails, git will output .rej files showing which lines couldn't match automatically. You can open these rejection files alongside the source code and apply the missing changes manually using standard text editing tools.
