Re: Issue 310 in xmonad: XMonad.Main.handle eats WM_NAME property changes

Updates: Status: Accepted Labels: Type-Defect Component-Core Comment #1 on issue 310 by byorgey: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 I can reproduce this. Could a core developer take a look at this? If it is really as easy as amdragon suggests (and the suggested fix wouldn't be undesirable for other reasons), this ticket has no excuse for still being open. =) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Updates: Status: Patch Comment #2 on issue 310 by daniel.schoepe: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 I can also confirm this behaviour and that amdragon's fix works as expected. I haven't noticed any other layouts misbehaving and think that would be unlikely. I attached a patch so it doesn't get lost. Until it is applied, one can get the same behaviour by adding this to one's xmonad.hs: broadcastPropChange ev@(PropertyEvent { ev_event_type = t, ev_atom = a }) | t == propertyNotify && a == wM_NAME = broadcastMessage ev >> return (All True) broadcastPropChange _ = return (All True) .. handleEventHook = .. <+> broadcastPropChange Attachments: broadcast_propchange.dpatch 3.7 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Updates: Status: Fixed Comment #3 on issue 310 by SpencerJanssen: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 Applied. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
participants (1)
-
codesite-noreply@google.com