On Tue 24 Feb 2015 at 15:01:48 +0100, Alexander Klein wrote: > Hello, > > I use ctwm 3.8.2 on FreeBSD 10.1, and I keep having a few issues with key > bindings, especially f.warpring. The following bindings are in effect: > > "Left" = m4 : all : f.warpring "prev" > "Right" = m4 : all : f.warpring "next" > > Usually, I can cycle through the windows using win+Left win+Right. Every > once in a while, however, ctwm seems to forget the key bindings, and starts > to send the respective keyboard events to the windows themselves. This seems > to be the case, especially, after X has used any DMPS-features.
Could it be that somehow for instance scroll lock or num lock or something like that is engaged/disengaged? If you don't ignore a modifier (and you can in practice only ignore one), it influences which bindings are matched. > Another thing that I never managed to get to work is the combination of > ClickToFocus and warpring. I even tried a few user-defined functions in > order to force the keyboard focus to be in the window that f.warpring cycled > to, but this never quite worked, unless the "focus follows mouse" model was > used. A quick look at the code shows nothing that pretends to focus the target window. Only to raise it. I'd say it makes sense to focus it as well, in all focus models. I suppose that is an easy enough change to make, unless there is some drawback that I'm missing? > Any ideas what else I could try? Your mentioning of user-defined functions makes me think that a command to focus a particular window does exist (f.focus). Does it have the desired effect? Or maybe if you use a user-defined function with f.warpring "next", f.focus it doesn't know which window to focus? Some change here could help too, perhaps. > Thank you, > Alexander -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl -- 'this bath is too hot.'
pgpxKJ3cJbAvz.pgp
Description: PGP signature
