That sounds unusual, I tried both xterm and uxterm and they both
behave like I expect with registering key presses including F1 as long
as that xterm has focus no matter if the mouse is someplace else.  It
is the same behavior as other terminals and other programs.
Style "*" SloppyFocus

The left click xterm menu has a Secure Keyboard option.  In this mode
the xterm grabs the keyboard and doesn't give it up until it is
minimized or you ask it to give it up.  The idea is nothing else can
grab your keyboard while you type in a password, for the paranoid I
guess.  You might want to read about it in the man page see securekbd,
and see if once it grabs the keyboard if it still gets the keys no
matter where the mouse is (what I see).

The behavior you describe is something like what ssh-askpass-gnome
does, only in that case it grabs the keyboard focus, then ignores all
keys until the mouse is over it.  I find this annoying because I have
hotkeys to move the mouse around, which don't work because it has a
keyboard grab.

On Wed, Mar 09, 2022 at 09:07:07AM +0100, n952162 wrote:
> xterm*VT100.Translations only when mouse is over the window with focus
> Is this a bug or a feature?
> For me, it's a serious problem.
> (click to focus)
> In particular, I'm talking about the function keys.  These are NOT
> mapped in fvwm, but in xterm.
> Pressing a function key, like F1, always writes to the window with focus,
> but only performs the X11/xterm translations with the mouse is hovering
> of the window with focus.
> So, I always have to move the mouse to the window to be able to write to
> the window.
> Note that I can visit various windows with keyboard shortcuts, so
> there's no natural
> correspondence with mouse position and window focus.
> fvwm 2.6.6 compiled on Oct 10 2016 at 00:25:52
> with support for: ReadLine, XPM, PNG, SVG, Shape, XShm, SM, Bidi text,
> Xinerama, XRender, XCursor, XFT, NLS

David Fries <>

Reply via email to