On Thu, Oct 05, 2017 at 07:40:30PM -0400 I heard the voice of Steve Litt, and lo! it spake thus: > > Sometimes, usually after I use one of my self-defined hotkeys, ctwm > goes into a state in which it appears not to hear keypresses or > mouseclicks. You can still move the mouse pointer around, but can't > do anything else.
The usual reason for that is some modifier's in effect (commonly something like caps lock or the like), so the bindings all _work_, you just haven't defined any that apply with caps lock or whatever. There are the IgnoreLockModifier and IgnoreModifier config options to "deal" with these cases, though with their own mildly fugly side effects. > When this happens, issuing a kill -s SIGHUP $CTWMPID from a virtual > terminal either does nothing or makes it worse (now you can't move > the mouse). Well, if it's a modifier thing, you'd expect it to do nothing, since the modifier is still in place. I'm not sure how it could gum up mouse movement though; that pretty much all happens way up in X without ctwm's intervention at all. So if you're getting _that_, I'd look upstack at stuff. SIGHUP just invokes the same codepath as f.restart. > I was hoping someone on the list has seen this before and knows how > to bust out of it without going Ctrl+Alt+F1 and then ctrl+C'ing out > of the startx command that ran ctwm in the first place. I've gone back and forth a half dozen times over the year, but I'm currently in the state where I run a special xterm as the final command instead of ctwm, so if necessary I can kill off the WM wholesale and restart from scratch without killing off the X session. Or alternately, so I can screw up code adjustments and blow up ctwm without killing off X. If I weren't perfect, I mean. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
