On Wed, Dec 13, 2006 at 01:43:02PM +0100, Anselm R. Garbe wrote:
> On Wed, Dec 13, 2006 at 12:22:11PM +0100, Sander van Dijk wrote:
> > Well then I guess the "fix" at the dwm side is simple: add a note to
> > the CAVEATS section of dwm.1 explaining the situation and advising to
> > use the 1.4 series until Sun fixes this (instead of adding workarounds
> > for workarounds for ...).
> >
> > Greetings, Sander.
> >
> > PS. I know your emotions and share them, but please word things in an
> > "acceptable" way in the manpage ;-)
>
> I hope the caveat section I pushed is acceptable now ;)
> I also added a comment to that bug description. When re-reading
> the bug evaluation, I come to the conclusion, that recent
> snapshots of JDK1.6 or JDK1.6+ might fix the problem...
> We'll see.
>
Hi Anselm,
Many thanks for sorting this problem out! Definitely Java's fault then.
I'm also shocked at the way they implemented the backend, very
amateurish.
I happen to work on a large space project where we have chosen to do all
our data processing in Java, so I'm stuck with this problem (although WM
details are not really something we worry about). I'm quite happy with
Java othwerise, but let's not get into a discussion on its merits here!
cheers,
Anthony
Received on Wed Dec 13 2006 - 17:54:41 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 14:33:48 UTC