| 1 |
On 4/23/22 06:04, David Fries wrote: |
| 2 |
> That sounds unusual, I tried both xterm and uxterm and they both |
| 3 |
> behave like I expect with registering key presses including F1 as long |
| 4 |
> as that xterm has focus no matter if the mouse is someplace else. It |
| 5 |
> is the same behavior as other terminals and other programs. |
| 6 |
> Style "*" SloppyFocus |
| 7 |
> |
| 8 |
> The left click xterm menu has a Secure Keyboard option. In this mode |
| 9 |
> the xterm grabs the keyboard and doesn't give it up until it is |
| 10 |
> minimized or you ask it to give it up. The idea is nothing else can |
| 11 |
> grab your keyboard while you type in a password, for the paranoid I |
| 12 |
> guess. You might want to read about it in the man page see securekbd, |
| 13 |
> and see if once it grabs the keyboard if it still gets the keys no |
| 14 |
> matter where the mouse is (what I see). |
| 15 |
> |
| 16 |
> The behavior you describe is something like what ssh-askpass-gnome |
| 17 |
> does, only in that case it grabs the keyboard focus, then ignores all |
| 18 |
> keys until the mouse is over it. I find this annoying because I have |
| 19 |
> hotkeys to move the mouse around, which don't work because it has a |
| 20 |
> keyboard grab. |
| 21 |
|
| 22 |
|
| 23 |
Ah, sorry, I should have mentioned, ClickToFocus. |
| 24 |
|
| 25 |
I am certain this is not some kind of subtle interplay of features, like |
| 26 |
you're suggesting. ClickToFocus does not behave this way on Linux, just |
| 27 |
on Cygwin. |
Archives