I wrote (about keybindings for F1 and F12)
> [[...]] after running ctwm for a while (anywhere from a few
> minutes to some hours, depending on my usage), these keys stop working
> (they no longer raise/lower the current window). I've checked with
> 'xev' and these keys are still generating keypress X events.
On Sat, 9 Oct 2021 14:48:10 +0200
Rhialto <rhia...@falu.nl> wrote:
> The most common thing that causes such a symptom is having Caps Lock
> pressed. It counts as a modifier, so pressing CapsLock + F1 doesn't
> match your mapping.
On Sat, Oct 09, 2021 at 10:12:09PM +0200, Carl Svensson wrote:
> I personally find Num Lock to be at least as great a culprit.
> I've added the following to my .ctwmrc (Num Lock may be a
> different modifier on your system):
>
> # Ignore Num Lock and Caps Lock
> IgnoreModifier {
> lock
> m2
> }
Brilliant! You are indeed both correct -- my problem was mainly Num-Lock
(which on my keyboard is needed in order to enable the numeric keypad),
but when I tested, Caps-Lock also causes my bindigs to be ignored.
I've added Carl's suggested stanza to my ~/.ctwmrc and my keybindings now
work perfectly regardless of either Num-lock or Caps-Lock.
Thanks 1L<<20 to both of you!
All the best, keep safe and COVID-free,
--
-- "Jonathan Thornburg [remove color- to reply]" <jthorn4...@pink-gmail.com>
on the west coast of Canada, eh?
"There was of course no way of knowing whether you were being watched
at any given moment. How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork. It was even conceivable
that they watched everybody all the time." -- George Orwell, "1984"
