+.BR st(1).
+.TP
+.B Super\-L
+Lock screen,
+.BR slock.
+.TP
+.B Super\-w
+Web browser
+.BR firefox.
+.TP
+.B Super\-n
+Network
+.BR nmtui.
+.TP
+.B Super\-v
+View system status
+.BR htop.
+.TP
+.B Super\-s
+Sound
+.BR alsamixer.
+.SS Mouse commands
+.TP
+.B Super\-Button1
+Move focused window while dragging. Tiled windows will be toggled to the floating state.
+.TP
+.B Super\-Button2
+Toggles focused window between floating and tiled state.
+.TP
+.B Super\-Button3
+Resize focused window while dragging. Tiled windows will be toggled to the floating state.
+.SH CUSTOMIZATION
+dwm is customized by creating a custom config.h and (re)compiling the source
+code. This keeps it fast, secure and simple.
+.SH SIGNALS
+.TP
+.B SIGHUP - 1
+Restart the dwm process.
+.TP
+.B SIGTERM - 15
+Cleanly terminate the dwm process.
+.SH SEE ALSO
+.BR dmenu (1),
+.BR st (1)
+.SH ISSUES
+Java applications which use the XToolkit/XAWT backend may draw grey windows
+only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
+JDK 1.6 versions, because it assumes a reparenting window manager. Possible workarounds
+are using JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or setting the
+environment variable
+.BR AWT_TOOLKIT=MToolkit
+(to use the older Motif backend instead) or running
+.B xprop -root -f _NET_WM_NAME 32a -set _NET_WM_NAME LG3D
+or
+.B wmname LG3D
+(to pretend that a non-reparenting window manager is running that the
+XToolkit/XAWT backend can recognize) or when using OpenJDK setting the environment variable
+.BR _JAVA_AWT_WM_NONREPARENTING=1 .
+.SH BUGS