[xmonad] xmonad 0.8 release candidate

Aaron Culich aculich at seas.harvard.edu
Fri Aug 29 06:40:55 EDT 2008


Joachim Breitner <nomeata at debian.org> writes:
> Am Donnerstag, den 28.08.2008, 15:06 -0400 schrieb Gwern Branwen:
>> On 2008.08.26 23:32:19 +0200, Joachim Breitner <mail at joachim-breitner.de> scribbled 1.6K characters:
>> > Hi,
>> >
>> > Am Dienstag, den 26.08.2008, 16:23 -0400 schrieb Gwern Branwen:
>> > > Or how about this UpdatePointer patch
>> > > <http://www.haskell.org/pipermail/xmonad/2008-June/005845.html>? No
>> > > comments, applies cleanly, and doesn't look fatally flawed to me.
>> >
>> > I know that _something_ behaved differently when I packaged and
>> > installed the release candidate, although I wasn’t sure until you
>> > notified me of this. I must have had it applied locally before.
>> 
>> That's interesting. So you didn't see any problems with this patch?
>> Did it get more widely used? If it's been de facto tested extensively
>> already, application would be a good idea.
>
> I’ve been using it since it was posted, and it’s fine. Without it, I
> sometimes have mouse jumps away from popped up menus, just because
> Xmonad felt it had to run loghook for some reason. From my POV, this is
> tested and can be considered a bug fix, not a new feature, and therefore
> could, with some goodwill, be applied in a release freeze :-)
>
> I don’t know of anyone else using it, so if anyone on this list uses
> UpdatePointer without these patches, please speak up.

I was not aware of this patch because I haven't followed the patches
much in a while, but I would consider this patch to be a bug fix that
I would be very thankful for. Most of the time the bug is just
annoying, but occasionally it can make things frustratingly unusable--
not often, but just enough. I've learned to live with the problem like
hiking with a pebble in one's shoe.

I don't know how many people actually use UpdatePointer, but I suspect
that for those who do use it and experience this bug, most would
probably be very happy to have this fix.

-Aaron


More information about the xmonad mailing list