issue with modkey on search key on chromebook with awesomewm

sepharoth213 · 2014-07-03 10:27:37

I recently got my c720 and it's fantastic, but there's a weird problem with the modkey functionality that I need to fix before it drives me insane. I use colemak, and that involves having the caps lock key mapped to backspace. In the case of this computer, the caps lock key has been replaced with a search key, which is by default bound to super (windows key). So in I go to make the search key backspace and the backspace key super using xmodmap:

keycode 133 = BackSpace BackSpace BackSpace BackSpace BackSpace BackSpace
keycode 22 = Super_L NoSymbol Super_L

This, at first glance, works perfectly. Using the backspace key as a modifier works, and the search key functions as a backspace key, and even repeats if I hold it. However, while it is being held, it also still works as a super key. This causes only 1 issue, though it is kind of large: if I ever backspace and hold the key down slightly too long, the next letter I type could set off an awesomewm button. Some common ones are super+q, w, or f, which are currently bound to the browser, terminal, and text editor tabs in my awesome, super + h and i, which are resize, and super + k, which is minimize.

Awful (awesome's library for things) has pretty mediocre documentation, and is especially lacking in how this part works. I have tried changing the backspace to a different modkey (Mod5 -- which is menu) to no avail. Documentation here shows that 'Valid modifiers are: Any, Mod1, Mod2, Mod3, Mod4, Mod5, Shift, Lock and Control.' So since Mod4 is out of the question as that is the problem, and Shift, Control, and Mod1 (alt) can't be used, Mod2, Mod3, Mod5, and Lock are the only options left.

I think Mod5 is menu, I found that on some post somewhere which I can't locate. I'm fairly certain Mod2 and Mod3 are scroll lock and num lock, and Lock is caps lock.

I can see three possible solutions: I find a way to get one of the other modkeys working and set my backspace key to that so that the search key firing super doesn't do anything, or I find a way to get my search key to stop firing super. A last resort would be to tell awesome to ignore hotkeys pressed a small amount of time after backspace is pressed, or for it detect the keycode, though I'm not comfortable enough in lua or awesome to get that working at all.

I've checked xev and it doesn't seem to see anything weird going on with my search key, so I'm at a loss. Can anyone help?

Trilby · 2014-07-03 11:06:08

Isn't this thread the same question? (with an answer)

sepharoth213 · 2014-07-03 11:09:07

Well, not quite, since I've already found my search key and mapped it to backspace. It's just still sending super at the same time.

Arch Linux

#1 2014-07-03 10:27:37

issue with modkey on search key on chromebook with awesomewm

#2 2014-07-03 11:06:08

Re: issue with modkey on search key on chromebook with awesomewm

#3 2014-07-03 11:09:07

Re: issue with modkey on search key on chromebook with awesomewm

Board footer