3 dwm \- dynamic window manager
8 dwm is a dynamic window manager for X. It manages windows in tiled, maximised
9 and floating layouts. Either layout can be applied dynamically, optimising the
10 environment for the application in use and the task performed.
12 In tiled layout windows are managed in a master and stacking area. The master
13 area contains the window which currently needs most attention, whereas the
14 stacking area contains all other windows. In maximised layout all windows are
15 maximised to the screen size. In floating layout windows can be resized and
16 moved freely. Dialog windows are always managed floating, regardless of the
19 Windows are grouped by tags. Each window can be tagged with one or multiple
20 tags. Selecting certain tags displays all windows with these tags.
22 dwm contains a small status bar which displays all available tags, the layout,
23 the title of the focused window, and the text read from standard input. A
24 floating window is indicated with an empty square and a maximised
25 floating window is indicated with a filled square before the windows
26 title. The selected tags are indicated with a different color. The tags of
27 the focused window are indicated with a filled square in the top left
28 corner. The tags which are applied to one or more windows are indicated
29 with an empty square in the top left corner.
31 dwm draws a small border around windows to indicate the focus state.
35 prints version information to standard output, then exits.
40 is read and displayed in the status text area.
43 click on a tag label to display all windows with that tag, click on the layout
44 label toggles between tiled and floating layout.
47 click on a tag label adds/removes all windows with that tag to/from the view.
50 click on a tag label applies that tag to the focused window.
53 click on a tag label adds/removes that tag to/from the focused window.
56 .B Mod1\-Shift\-Return
61 Zooms/cycles current window to/from master area (tiled layout only).
64 Toggles to the previously selected tags.
70 Applies loating layout.
73 Applies maximised layout.
76 Toggles between layouts.
79 Shows/hides the status bar.
82 Decreases the master area width about 5% (tiled layout only).
88 Focus previous window.
91 Increases the master area width about 5% (tiled layout only).
94 Re-applies tagging rules to all windows.
96 .B Mod1\-Shift\-[1..n]
99 tag to current window.
102 Apply all tags to current window.
104 .B Mod1\-Control\-Shift\-[1..n]
107 tag to/from current window.
110 Close focused window.
112 .B Mod1\-Shift\-space
113 Toggle focused window between tiled and floating state.
116 View all windows with
121 View all windows with any tag.
123 .B Mod1\-Control\-[1..n]
124 Add/remove all windows with
126 tag to/from the view.
133 Move current window while dragging. Tiled windows will be toggled to the floating state.
136 Zooms/cycles current window to/from master area. If it is floating (but not fixed) it will be toggled to the tiled state instead.
139 Resize current window while dragging. Tiled windows will be toggled to the floating state.
141 dwm is customized by creating a custom config.h and (re)compiling the source
142 code. This keeps it fast, secure and simple.
146 The status bar may display
148 when dwm has been started by an X session manager like
150 because those close standard output before executing dwm.
152 Java applications which use the XToolkit/XAWT backend may draw grey windows
153 only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
154 JDK 1.6 versions, because it assumes a reparenting window manager. As a workaround
155 you can use JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or you
156 can set the following environment variable (to use the older Motif
158 .BR AWT_TOOLKIT=MToolkit .
160 Recent GTK 2.10.9+ versions contain a broken
162 file dialog implementation,
163 which requests to reconfigure its window size in an endless loop. However, its
164 window is still respondable during this state, so you can simply ignore the flicker
165 until a new GTK version appears, which will fix this bug, approximately
166 GTK 2.10.12+ versions.