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.
On Thu, Jan 20, 2011 at 9:33 AM, Kai Hendry wrote:
> Please let me know if you figure this problem out.
I now use wpa_cli -a and netplugd with a few scripts to stick it all together.
I use wpa_cli -a for wifi events, because netplugd does too much with
the device, always tries to keep it up.
If
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'
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
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
I think ifplugd also polls, it uses ethtool to detect changes.
I'll try netplug, which uses netlink(7).
Traditionally, this was solved by making wmiirc (1) emit "Start
wmiirc" to /event at startup and later (2) exit if they see "Start
wmiirc" inside their /event processing loop. In this manner, new
instances of wmiirc terminate previously existing ones.
I don't know why that mechanism was removed
