Hi Olaf,
Am 24.02.2015 um 22:16 schrieb Rhialto:
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.
Thank you, I hadn't noticed this before. Upon ignoring m2, which is
mapped to NumLock, the symptoms after DPMS have disappeared. Just a few
minutes ago, however, CTWM ignored its key bindings until I manually
switched to another workspace. The workspace that didn't react had an
instance of Chrome open, and of course the workspace manager, but
nothing else.
Or maybe if you use a user-defined function with
f.warpring "next", f.focus it doesn't know which window to focus?
I tried a number of combinations, but it never really worked. Usually,
the correct window was brought to the top, but another one would get the
focus, or sometimes none at all.
Best,
Alexander
--
Alexander Klein
Physiologisches Institut der JLU-Gießen
Aulweg 129
35392 Gießen
http://www.med.uni-giessen.de/physio/
