On Sat, Sep 11, 2010 at 03:59:41PM -0400, Benjamin Cathey wrote:
Kris
This is what I had thought originally. The behavior made me think
possibly something was running that was trapping keyboard input (like a
process that did not get a "&" after it). However this is not the case.
My old config was in .wmii-3.5/ however I moved .wmii to .wmii.orig
just to be sure.
Still no keyboard input works at all.
Any further thoughts? It's running on 'lucid' if that helps.
I can send any output of any commands/logs, etc that you think might help
Well, the easiest tests are,
ps ax | grep wmiirc # Should list 1 or 2 processes
wmiir read /keys # Should list all of your key bindings
wmiir read /event # Press some key bindings, should show up
If all else fails, try this from the console:
wmii -r python/wmiirc
--
Kris Maglione
You do not really understand something unless you can explain it to
your grandmother.
--Albert Einstein