XMonad.Hooks.UrgencyHook broken?

Hi, I have tried using XMonad.Hooks.UrgencyHook but can't get it to work -- despite following the docs for it. In my ~/xmonad/xmonad.hs file, I have main = xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "darkgreen", "-xs", "1"] } Yet when chatting via pidgin, which would send such an urgency hook, xmonad doesnt react to it. What's the best way of testing this? Is there something else i need to be doing to get this to work? i heard that rxvt-unicode can generate urgencyhook stuff -- how? Thanks! David.

On Sat, 19 Jan 2008 22:59:26 +0000
"David Chanters"
Yet when chatting via pidgin, which would send such an urgency hook, xmonad doesnt react to it.
I had the same problem. I eventually figured I should check the default plugins and there was one which controlled the urgent events: Message Notification. There's a checkbox for sending urgent events to the wm. After checking that, everything was fine. Regards, -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

On 19/01/2008, Ricardo Martins
On Sat, 19 Jan 2008 22:59:26 +0000 "David Chanters"
wrote: Yet when chatting via pidgin, which would send such an urgency hook, xmonad doesnt react to it.
I had the same problem. I eventually figured I should check the default plugins and there was one which controlled the urgent events: Message Notification. There's a checkbox for sending urgent events to the wm. After checking that, everything was fine.
Ok - i did this and restarted pidgin, and still nothing. Where would the dzen bar appear? i have other dzen instances running just fine. if it matters, here's the relevant lines from my config: statusBarCmd= "dzen2 -bg '#2c2c32' -fg 'grey70' -w 370 -x 0 -ta l -p -e ''" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "purple", "-fg", "white", "-xs", "-1"] } $ sConfig d Certainly I see nothing on screen 1 --- should I? And for how long, and where? I don't even know what I am supposed to be seeing. :) David.

On Sat, 19 Jan 2008 23:30:46 +0000
"David Chanters"
Ok - i did this and restarted pidgin, and still nothing. Where would the dzen bar appear? i have other dzen instances running just fine. if it matters, here's the relevant lines from my config:
statusBarCmd= "dzen2 -bg '#2c2c32' -fg 'grey70' -w 370 -x 0 -ta l -p -e ''" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "purple", "-fg", "white", "-xs", "-1"] } $ sConfig d
Certainly I see nothing on screen 1 --- should I? And for how long, and where? I don't even know what I am supposed to be seeing. :)
Hmm, shouldn't it be "1" instead of "-1" after "-xs"? I don't use Xinerama, so I don't know the behaviour with more than one screen, but the dzen notification should appear on top of your screen, for about 1 or two seconds. I'm far too ignorant about xmonad and dzen to be sure, actually. Test with gajim (jabber client), if you can. Its urgent events work correctly out of the box. Just make sure the conversation windows isn't focused. Regards, -- Ricardo Martins * scarybox.net * GPG key: 0x1308F1B4

On 19/01/2008, Ricardo Martins
On Sat, 19 Jan 2008 23:30:46 +0000 "David Chanters"
wrote: Ok - i did this and restarted pidgin, and still nothing. Where would the dzen bar appear? i have other dzen instances running just fine. if it matters, here's the relevant lines from my config:
statusBarCmd= "dzen2 -bg '#2c2c32' -fg 'grey70' -w 370 -x 0 -ta l -p -e ''" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "purple", "-fg", "white", "-xs", "-1"] } $ sConfig d
Certainly I see nothing on screen 1 --- should I? And for how long, and where? I don't even know what I am supposed to be seeing. :)
Hmm, shouldn't it be "1" instead of "-1" after "-xs"?
So it should -- changed, but *still* nothing. :(
I don't use Xinerama, so I don't know the behaviour with more than one screen, but the dzen notification should appear on top of your screen, for about 1 or two seconds. I'm far too ignorant about xmonad and dzen to be sure, actually.
Thanks though Is there some way to debug this? -- Thomas Adam

On 20/01/2008, David Chanters
On 19/01/2008, Ricardo Martins
wrote: On Sat, 19 Jan 2008 23:30:46 +0000 "David Chanters"
wrote: Ok - i did this and restarted pidgin, and still nothing. Where would the dzen bar appear? i have other dzen instances running just fine. if it matters, here's the relevant lines from my config:
statusBarCmd= "dzen2 -bg '#2c2c32' -fg 'grey70' -w 370 -x 0 -ta l -p -e ''" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "purple", "-fg", "white", "-xs", "-1"] } $ sConfig d
Certainly I see nothing on screen 1 --- should I? And for how long, and where? I don't even know what I am supposed to be seeing. :)
Hmm, shouldn't it be "1" instead of "-1" after "-xs"?
So it should -- changed, but *still* nothing. :(
I don't use Xinerama, so I don't know the behaviour with more than one screen, but the dzen notification should appear on top of your screen, for about 1 or two seconds. I'm far too ignorant about xmonad and dzen to be sure, actually.
Thanks though Is there some way to debug this?
Have you tried a basic config from a template? Such as on the wiki? Maybe it's something in your config? -- Thomas Adam

On 20/01/2008, Thomas Adam
On 20/01/2008, David Chanters
wrote: On 19/01/2008, Ricardo Martins
wrote: On Sat, 19 Jan 2008 23:30:46 +0000 "David Chanters"
wrote: Ok - i did this and restarted pidgin, and still nothing. Where would the dzen bar appear? i have other dzen instances running just fine. if it matters, here's the relevant lines from my config:
statusBarCmd= "dzen2 -bg '#2c2c32' -fg 'grey70' -w 370 -x 0 -ta l -p -e ''" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "purple", "-fg", "white", "-xs", "-1"] } $ sConfig d
Certainly I see nothing on screen 1 --- should I? And for how long, and where? I don't even know what I am supposed to be seeing. :)
Hmm, shouldn't it be "1" instead of "-1" after "-xs"?
So it should -- changed, but *still* nothing. :(
I don't use Xinerama, so I don't know the behaviour with more than one screen, but the dzen notification should appear on top of your screen, for about 1 or two seconds. I'm far too ignorant about xmonad and dzen to be sure, actually.
Thanks though Is there some way to debug this?
Have you tried a basic config from a template? Such as on the wiki? Maybe it's something in your config?
-- Thomas Adam
where do i find such a template? David.

Hy, in order to test urgency-hooks I used the attached program. urgent.c is the c source and urgent is the binary. For compiling from source read the comment on top of the file. Use it like this: $ sleep 10 && ./urgent Which sleeps 10 seconds and then sends out an urgency-hint. Pay attention: Using the urgent-program directlt without a sleep in front doesnt make sense imho. I hope this helps to debug this error. -- Dominik Bruhn mailto: dominik@dbruhn.de
participants (4)
-
David Chanters
-
Dominik Bruhn
-
Ricardo Martins
-
Thomas Adam