Post History
Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause. By inspecting the output of xev -event keyboard |...
Question
keyboard-event
#3: Post edited
by
Quasímodo
·
2021-10-24T15:07:03Z (over 2 years ago)
- Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause.
- By inspecting the output of `xev -event keyboard | grep -E '^Key|state'` for holding Pause and then pressing s,
- ```
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x20, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- ```
- we see that I succeeded in making Pause an Hyper modifier; However, it can't actually be used as a modifier since **the key is immediately released** (even though I didn't release it before pressing s).
- The same is detected by `showkey`: Holding Pause immediately outputs
- keycode 119 press
- keycode 119 release
- whereas holding another key (Insert) spams
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- as expected.
Why does this odd behavior happen with the Pause key? Is it a hardware thing (and thus unsolvable) or can it be addressed in the OS level?----Two webpages that may be helpful, but that I only partially understand:- [Keyboard scancodes](https://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html)- [What is the scancode of "Pause/Break" key?](https://stackoverflow.com/questions/38846347/what-is-the-scancode-of-pause-break-key)
- Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause.
- By inspecting the output of `xev -event keyboard | grep -E '^Key|state'` for holding Pause and then pressing s,
- ```
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x20, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- ```
- we see that I succeeded in making Pause an Hyper modifier; However, it can't actually be used as a modifier since **the key is immediately released** (even though I didn't release it before pressing s).
- The same is detected by `showkey`: Holding Pause immediately outputs
- keycode 119 press
- keycode 119 release
- whereas holding another key (Insert) spams
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- as expected.
- Why does this odd behavior happen with the Pause key? Is it a hardware thing (and thus unsolvable) or can it be addressed in the OS level?
#2: Post edited
by
Quasímodo
·
2021-10-24T14:53:58Z (over 2 years ago)
- Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause.
- By inspecting the output of `xev -event keyboard | grep -E '^Key|state'` for holding Pause and then pressing s,
- ```
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x20, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- ```
- we see that I succeeded in making Pause an Hyper modifier; However, it can't actually be used as a modifier since **the key is immediately released** (even though I didn't release it before pressing s).
- The same is detected by `showkey`: Holding Pause immediately outputs
- keycode 119 press
- keycode 119 release
- whereas holding another key (Insert) spams
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- as expected.
Why does this odd behavior happen with the Pause key? Is it a hardware thing (and thus unsolvable) or can it be addressed in the OS level?
- Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause.
- By inspecting the output of `xev -event keyboard | grep -E '^Key|state'` for holding Pause and then pressing s,
- ```
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x20, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
- KeyPress event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- KeyRelease event, serial 28, synthetic NO, window 0x800001,
- state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
- ```
- we see that I succeeded in making Pause an Hyper modifier; However, it can't actually be used as a modifier since **the key is immediately released** (even though I didn't release it before pressing s).
- The same is detected by `showkey`: Holding Pause immediately outputs
- keycode 119 press
- keycode 119 release
- whereas holding another key (Insert) spams
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- keycode 110 press
- as expected.
- Why does this odd behavior happen with the Pause key? Is it a hardware thing (and thus unsolvable) or can it be addressed in the OS level?
- ----
- Two webpages that may be helpful, but that I only partially understand:
- - [Keyboard scancodes](https://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html)
- - [What is the scancode of "Pause/Break" key?](https://stackoverflow.com/questions/38846347/what-is-the-scancode-of-pause-break-key)
#1: Initial revision
by
Quasímodo
·
2021-10-20T12:13:16Z (over 2 years ago)
Why is Pause/Break key is immediately released? Can that be fixed?
Since the Pause key is useless, I tried to map it to a modifier key. What is straightforward for other keys turned out not to work fine for Pause.
By inspecting the output of `xev -event keyboard | grep -E '^Key|state'` for holding Pause and then pressing s,
```
KeyPress event, serial 28, synthetic NO, window 0x800001,
state 0x0, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
KeyRelease event, serial 28, synthetic NO, window 0x800001,
state 0x20, keycode 127 (keysym 0xffed, Hyper_L), same_screen YES,
KeyPress event, serial 28, synthetic NO, window 0x800001,
state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
KeyRelease event, serial 28, synthetic NO, window 0x800001,
state 0x0, keycode 39 (keysym 0x73, s), same_screen YES,
```
we see that I succeeded in making Pause an Hyper modifier; However, it can't actually be used as a modifier since **the key is immediately released** (even though I didn't release it before pressing s).
The same is detected by `showkey`: Holding Pause immediately outputs
keycode 119 press
keycode 119 release
whereas holding another key (Insert) spams
keycode 110 press
keycode 110 press
keycode 110 press
keycode 110 press
keycode 110 press
as expected.
Why does this odd behavior happen with the Pause key? Is it a hardware thing (and thus unsolvable) or can it be addressed in the OS level?