remove old TODO and BUGS entries 10dfa658
the bug in the dwm man page is an (ancient) Java issue.

Thanks David and quinq for the patches and feedback!
Hiltjo Posthuma · 2018-05-12 19:14 4 file(s) · +4 −58
BUGS (deleted) +0 −44
1 -
---
2 -
3 -
18:17 < Biolunar> when i change my resolution in dwm (to a smaller one) and then back to the native, the top bar is not repainted. that's since 5.7.2, in 5.6 it worked fine
4 -
18:19 < Biolunar> is it just happening to me or a (known) bug?
5 -
18:24 < Biolunar> and in addition, mplayers fullscreen is limited to the small resolution after i changed it back to the native
6 -
7 -
reproducible with xrandr -s but not with --output and --mode, strange
8 -
9 -
---
10 -
11 -
yet another corner case:
12 -
open a terminal, focus another monitor, but without moving the mouse
13 -
pointer there
14 -
if there is no client on the other monitor to get the focus, then the
15 -
terminal will be unfocused but it will accept input
16 -
17 -
---
18 -
19 -
Donald Allen reported this:
20 -
21 -
starting emacs from dmenu in archlinux results in missing configure of emacs, but mod1-space or mod1-shift-space fix this problem. this problem is new and did not happen in 1.6 xorg servers
22 -
23 -
---
24 -
25 -
voltaic reports this:
26 -
27 -
When I use two monitors, one larger in resolution than the other, the
28 -
bar is drawn using the smaller x-dimension on both screens. I think
29 -
what's happening is that there are two bars drawn, but the short bar
30 -
is always on top of the long bar such that I can't see the information
31 -
under the short bar. If I switch to the small screen, hide the short
32 -
bar, and then switch to the large screen, the long bar is drawn
33 -
correctly.
34 -
35 -
A similar problem occurs when I have started dwm on a small resolution
36 -
monitor (laptop screen) and then I switch to a large external display.
37 -
When I do this, the bar itself is drawn for the original smaller
38 -
resolution, but the information to be printed on the bar is
39 -
right-aligned for a longer bar. So what I see is a bar that has the
40 -
right hand side of it cut-off. See attached screenshot.
41 -
42 -
I am using standard options for xrandr such as --output VGA1 --auto, etc.
43 -
44 -
---
Makefile +1 −1
35 35
dist: clean
36 36
	@echo creating dist tarball
37 37
	@mkdir -p dwm-${VERSION}
38 -
	@cp -R LICENSE TODO BUGS Makefile README config.def.h config.mk \
38 +
	@cp -R LICENSE Makefile README config.def.h config.mk \
39 39
		dwm.1 drw.h util.h ${SRC} dwm.png transient.c dwm-${VERSION}
40 40
	@tar -cf dwm-${VERSION}.tar dwm-${VERSION}
41 41
	@gzip dwm-${VERSION}.tar
TODO (deleted) +0 −4
1 -
- add a flag to Key to execute the command on release (needed for commands
2 -
		affecting the keyboard grab, see scrot -s for example)
3 -
- add updategeom() hook for external tools like dzen
4 -
- consider onscreenkeyboard hooks for tablet deployment
dwm.1 +3 −9
158 158
.SH SEE ALSO
159 159
.BR dmenu (1),
160 160
.BR st (1)
161 -
.SH BUGS
161 +
.SH ISSUES
162 162
Java applications which use the XToolkit/XAWT backend may draw grey windows
163 163
only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early
164 164
JDK 1.6 versions, because it assumes a reparenting window manager. Possible workarounds
172 172
(to pretend that a non-reparenting window manager is running that the
173 173
XToolkit/XAWT backend can recognize) or when using OpenJDK setting the environment variable
174 174
.BR _JAVA_AWT_WM_NONREPARENTING=1 .
175 -
.P
176 -
GTK 2.10.9+ versions contain a broken
177 -
.BR Save\-As
178 -
file dialog implementation,
179 -
which requests to reconfigure its window size in an endless loop. However, its
180 -
window is still respondable during this state, so you can simply ignore the flicker
181 -
until a new GTK version appears, which will fix this bug, approximately
182 -
GTK 2.10.12+ versions.
175 +
.SH BUGS
176 +
Send all bug reports with a patch to hackers@suckless.org.