summaryrefslogtreecommitdiff
path: root/dwm.1
diff options
context:
space:
mode:
authorHiltjo Posthuma <hiltjo@codemadness.org>2018-05-12 19:14:19 +0200
committerHiltjo Posthuma <hiltjo@codemadness.org>2018-05-12 19:14:19 +0200
commit10dfa65860d770cbce2cdaf67618f44f726a27c3 (patch)
tree4784f5ec39b0b6478e92520025c42f10ccdbf5f8 /dwm.1
parent3bd8466e93b2c81be86e67c6ecdda4e1d240fe4b (diff)
remove old TODO and BUGS entries
the bug in the dwm man page is an (ancient) Java issue. Thanks David and quinq for the patches and feedback!
Diffstat (limited to 'dwm.1')
-rw-r--r--dwm.112
1 files changed, 3 insertions, 9 deletions
diff --git a/dwm.1 b/dwm.1
index e3b2c38..13b3729 100644
--- a/dwm.1
+++ b/dwm.1
@@ -158,7 +158,7 @@ code. This keeps it fast, secure and simple.
.SH SEE ALSO
.BR dmenu (1),
.BR st (1)
-.SH BUGS
+.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
@@ -172,11 +172,5 @@ or
(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 .
-.P
-GTK 2.10.9+ versions contain a broken
-.BR Save\-As
-file dialog implementation,
-which requests to reconfigure its window size in an endless loop. However, its
-window is still respondable during this state, so you can simply ignore the flicker
-until a new GTK version appears, which will fix this bug, approximately
-GTK 2.10.12+ versions.
+.SH BUGS
+Send all bug reports with a patch to hackers@suckless.org.