I tried changing the shell to bash and it still didn't work. The fix at
that link did though, so at least it works now.
-Eitan
On 02/26/2011 02:33 AM, Thomas Dahms wrote:
It was the wrong wmiirc turns out. I was editing /etc/wmii-hg/wmiirc
and I was thinking about how the keybindings aren't t
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.
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
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
On Thu, Feb 24, 2011 at 12:14 PM, Benjamin R. Haskell
wrote:
> running the 'wmiirc' action just
> spawned a second instance of wmiirc (resulting in event doubling, e.g.
> keystroke that spawns a new terminal spawned two new terminals).
Traditionally, this was solved by making wmiirc (1) emit "Sta
On Thu, 24 Feb 2011, Suraj Kurapati wrote:
On Thu, Feb 24, 2011 at 11:25 AM, Benjamin R. Haskell wrote:
exec'ing wmii via the 'action' menu, which borks multi-monitor
layouts; anyone have a better way?
Have your wmiirc re-exec itself (as opposed to re-execing wmii).
Hmm. Makes sense. Does
On Thu, Feb 24, 2011 at 11:25 AM, Benjamin R. Haskell
wrote:
> exec'ing wmii via the 'action' menu, which borks multi-monitor layouts;
> anyone have a better way?
Have your wmiirc re-exec itself (as opposed to re-execing wmii).
On Wed, 23 Feb 2011, Eitan Goldshtrom wrote:
I tried that just now and it didn't work. I also tried a few
variations that each didn't work. I checked the "keys" file and it
looks like the 2 key combinations aren't in the file. I thought they
would be added because of the event declarations, bu
I tried that just now and it didn't work. I also tried a few variations
that each didn't work. I checked the "keys" file and it looks like the 2
key combinations aren't in the file. I thought they would be added
because of the event declarations, but am I supposed to add them
manually or someth
On Tue, 22 Feb 2011, Eitan Goldshtrom wrote:
Hi. So I read through as much as I could find on the subject of
defining my own keybindings. I can see how to do it from the 9P
virtual filesystem that wmii has setup, but I am under the impression
that it can be done moreproperly?...via wmiirc_
Hi. So I read through as much as I could find on the subject of defining
my own keybindings. I can see how to do it from the 9P virtual
filesystem that wmii has setup, but I am under the impression that it
can be done moreproperly?...via wmiirc_local and the local_events()
function. Unfortu
13 matches
Mail list logo
