It was the wrong wmiirc turns out. I was editing /etc/wmii-hg/wmiirc and
I was thinking about how the keybindings aren't the only thing that
wasn't working, so I ran a locate on wmiirc and found out I have a
/usr/local/etc/wmii-hg/wmiirc. Putting the key bindings in there made
them work. But I'm still confused about why they don't work when I put
them in wmiirc_local in the local_events() function.
-Eitan
On 02/25/2011 12:50 PM, Benjamin R. Haskell wrote:
On Fri, 25 Feb 2011, Eitan Goldshtrom wrote:
I've put the following directly into the events() function of my
wmiirc script in the KeyGroup Other section
Key $MODKEY-z
amixer sset PCM 4+ &
Key $MODKEY-v
eval wmiir setsid amixer sset PCM 4+ &
I've since quit wmii, logged out, logged back in, and started X and
wmii again. Still the key bindings don't work. When I test each of
those commands in a terminal it has the desired effect. I'm at a loss
at this point as to why it doesn't work. Is there a way for me to
check and see if anything is happening at all, even though my volume
isn't actually changing?
Try something interactive to see that keys are being reloaded (maybe
you're editing the wrong wmiirc?):
Key $MODKEY-z
xmessage blahblah &
or something that creates an obvious change:
Key $MODKEY-z
wmiir xwrite /ctl view "CHANGED"
Maybe amixer isn't in your $PATH by the time wmii starts:
Key $MODKEY-z
$HOME/local-stuff/amixer sset PCM 4+ &
Or just log the errors, and go from there:
Key $MODKEY-z
amixer sset PCM 4+ >$HOME/amixer.stdout 2>$HOME/amixer.stderr &
