changed plus key to MODKEY-Shift-plus (US-layout restrictions ;)

[dwm.git] / dwm.1

diff --git a/dwm.1 b/dwm.1
index a8fb40a..084c64e 100644 (file)
--- a/dwm.1
+++ b/dwm.1
@@ -70,6 +70,12 @@ Grow master area (tiling mode only).
 .B Mod1-s
 Shrink master area (tiling mode only).
 .TP
 .B Mod1-s
 Shrink master area (tiling mode only).
 .TP

+.B Mod1-Shift-plus
+Increase clients of master area (tiling mode only).
+.TP
+.B Mod1-minus
+Decrease clients of master area (tiling mode only).
+.TP

 .B Mod1-Shift-[1..n]
 Apply
 .RB nth
 .B Mod1-Shift-[1..n]
 Apply
 .RB nth

@@ -122,9 +128,17 @@ dwm is customized by creating a custom config.h and (re)compiling the source
 code. This keeps it fast, secure and simple.
 .SH CAVEATS
 The status bar may display
 code. This keeps it fast, secure and simple.
 .SH CAVEATS
 The status bar may display

-.BR "broken pipe"
-when dwm has been started by
+.BR "EOF"
+when dwm has been started by an X session manager like

 .BR xdm (1),
 .BR xdm (1),

-because it closes standard output before executing dwm.
+because those close standard output before executing dwm.
+.P
+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. As a workaround
+you can use JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or you
+can set the following environment variable (to use the older Motif
+backend instead):
+.BR AWT_TOOLKIT=MToolkit .

 .SH SEE ALSO
 .BR dmenu (1)
 .SH SEE ALSO
 .BR dmenu (1)