Ygtjki

Why is my log file so massive? 22gb. I am running log backups

"My colleague's body is amazing"

Is "plugging out" electronic devices an American expression?

Are objects structures and/or vice versa?

Where to refill my bottle in India?

Patience, young "Padovan"

Are cabin dividers used to "hide" the flex of the airplane?

Email Account under attack (really) - anything I can do?

Was there ever an axiom rendered a theorem?

How to deal with fear of taking dependencies

I see my dog run

What's the difference between repeating elections every few years and repeating a referendum after a few years?

Hosting Wordpress in a EC2 Load Balanced Instance

"listening to me about as much as you're listening to this pole here"

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

Shall I use personal or official e-mail account when registering to external websites for work purpose?

New order #4: World

Crop image to path created in TikZ?

Where else does the Shulchan Aruch quote an authority by name?

How to move the player while also allowing forces to affect it

Does a dangling wire really electrocute me if I'm standing in water?

Is this food a bread or a loaf?

How to manage monthly salary

What happens when a metallic dragon and a chromatic dragon mate?

Cannot map a hotkey on my keyboard (XF86Mail)

Declare a new modifier key with XKBProgrammatic way to install xkb keyboard layoutHow do I type punctuation characters on my localized keyboard?Can no longer switch keyboard layouts in xfcekeyboard layout switching - non-working hotkeys in cyrillic layoutUnable to switch to Dvorak layoutHow to change keyboard settings of the active user using udev and setxkbmap?Map right Alt to Ctrl keyKeyboard layout keys aren't maintained on debiansetxkbmap -layout us,pt doesn't work

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

I had the following problem:

I wanted to make use of some Hotkeys on my keyboard (I am using Openbox, but it should not make a difference.)

Most of my keybinds worked just fine (XF86AudioRaiseVolume, XF86AudioLowerVolume, etc.).

However, I got no response to
XF86Mail

keyboard-layout xkb

share|improve this question

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

add a comment | 

1

I had the following problem:

I wanted to make use of some Hotkeys on my keyboard (I am using Openbox, but it should not make a difference.)

Most of my keybinds worked just fine (XF86AudioRaiseVolume, XF86AudioLowerVolume, etc.).

However, I got no response to
XF86Mail

keyboard-layout xkb

share|improve this question

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

add a comment | 

I had the following problem:

I wanted to make use of some Hotkeys on my keyboard (I am using Openbox, but it should not make a difference.)

Most of my keybinds worked just fine (XF86AudioRaiseVolume, XF86AudioLowerVolume, etc.).

However, I got no response to
XF86Mail

keyboard-layout xkb

share|improve this question

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

share|improve this question

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

share|improve this question

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

edited Apr 5 at 20:49

Rui F Ribeiro

42k1483142

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

asked Apr 5 at 17:07

Zoltan K.Zoltan K.

1726

1 Answer
1

active

oldest

votes

0

1) Using xev I found that the key does work.

2) Inspecting the output of xev for known "good" keys, and not-working ones (XF86Mail), I found a difference:

Works in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70102367, (1618,-868), root:(3219,29),
 state 0x10, keycode 158 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

Does not work in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70103895, (1618,-868), root:(3219,29),
 state 0x10, keycode 223 (keysym 0x1008ff19, XF86Mail), same_screen YES,
--> XKeysymToKeycode returns keycode: 163
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

So, there is a plethora of options to choose from:

1. keycode: 163 (0xA3)


2. keycode: 223 (0xDF)


3. "XF86Mail"

Tried all of them, and the only one working was 0xDF. (<keybind key="0xDF"> in the openbox config)

Judging by the numbers, since the XF86WWW has the keycode 158, XF86Mail, the key next to it on the keyboard would probably had originally the keycode 163, but then a software layer changed it.

I started to dig into stuff like xmodmap, and an archwiki guide, but then I did not have to understand whatever is going on, xev alone gave me the solution, once I was able to understand it.

share|improve this answer

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510764%2fcannot-map-a-hotkey-on-my-keyboard-xf86mail%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

1) Using xev I found that the key does work.

2) Inspecting the output of xev for known "good" keys, and not-working ones (XF86Mail), I found a difference:

Works in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70102367, (1618,-868), root:(3219,29),
 state 0x10, keycode 158 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

Does not work in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70103895, (1618,-868), root:(3219,29),
 state 0x10, keycode 223 (keysym 0x1008ff19, XF86Mail), same_screen YES,
--> XKeysymToKeycode returns keycode: 163
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

So, there is a plethora of options to choose from:

1. keycode: 163 (0xA3)


2. keycode: 223 (0xDF)


3. "XF86Mail"

Tried all of them, and the only one working was 0xDF. (<keybind key="0xDF"> in the openbox config)

Judging by the numbers, since the XF86WWW has the keycode 158, XF86Mail, the key next to it on the keyboard would probably had originally the keycode 163, but then a software layer changed it.

I started to dig into stuff like xmodmap, and an archwiki guide, but then I did not have to understand whatever is going on, xev alone gave me the solution, once I was able to understand it.

share|improve this answer

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

add a comment | 

0

1) Using xev I found that the key does work.

2) Inspecting the output of xev for known "good" keys, and not-working ones (XF86Mail), I found a difference:

Works in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70102367, (1618,-868), root:(3219,29),
 state 0x10, keycode 158 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

Does not work in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70103895, (1618,-868), root:(3219,29),
 state 0x10, keycode 223 (keysym 0x1008ff19, XF86Mail), same_screen YES,
--> XKeysymToKeycode returns keycode: 163
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

So, there is a plethora of options to choose from:

1. keycode: 163 (0xA3)


2. keycode: 223 (0xDF)


3. "XF86Mail"

Tried all of them, and the only one working was 0xDF. (<keybind key="0xDF"> in the openbox config)

Judging by the numbers, since the XF86WWW has the keycode 158, XF86Mail, the key next to it on the keyboard would probably had originally the keycode 163, but then a software layer changed it.

I started to dig into stuff like xmodmap, and an archwiki guide, but then I did not have to understand whatever is going on, xev alone gave me the solution, once I was able to understand it.

share|improve this answer

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

add a comment | 

1) Using xev I found that the key does work.

2) Inspecting the output of xev for known "good" keys, and not-working ones (XF86Mail), I found a difference:

Works in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70102367, (1618,-868), root:(3219,29),
 state 0x10, keycode 158 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

Does not work in keybind:

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70103895, (1618,-868), root:(3219,29),
 state 0x10, keycode 223 (keysym 0x1008ff19, XF86Mail), same_screen YES,
--> XKeysymToKeycode returns keycode: 163
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

So, there is a plethora of options to choose from:

1. keycode: 163 (0xA3)


2. keycode: 223 (0xDF)


3. "XF86Mail"

Tried all of them, and the only one working was 0xDF. (<keybind key="0xDF"> in the openbox config)

Judging by the numbers, since the XF86WWW has the keycode 158, XF86Mail, the key next to it on the keyboard would probably had originally the keycode 163, but then a software layer changed it.

I started to dig into stuff like xmodmap, and an archwiki guide, but then I did not have to understand whatever is going on, xev alone gave me the solution, once I was able to understand it.

share|improve this answer

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70102367, (1618,-868), root:(3219,29),
 state 0x10, keycode 158 (keysym 0x1008ff2e, XF86WWW), same_screen YES,
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

KeyRelease event, serial 48, synthetic NO, window 0x2000001,
 root 0x1e3, subw 0x0, time 70103895, (1618,-868), root:(3219,29),
 state 0x10, keycode 223 (keysym 0x1008ff19, XF86Mail), same_screen YES,
--> XKeysymToKeycode returns keycode: 163
 XLookupString gives 0 bytes: 
 XFilterEvent returns: False

share|improve this answer

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726

answered Apr 5 at 17:20

Zoltan K.Zoltan K.

1726