Issue with keybinds in colemak

[RoastPotatoes]

When I change to colemak which is the main layout that I use. Most of the keybinds become defunct, but it is not all. alt + 'K' for example still functions but then alt + 'j' does not.

[sulami]

On Wed, Mar 25, 2015 at 12:00:40PM -0700, RoastPotatoes wrote:

When I change to colemak which is the main layout that I use. Most of the keybinds become defunct, but it is not all. alt + 'K' for example still functions but then alt + 'j' does not.

Okay, I don't have a lot of experience with non-qwerty layouts, so I might need a day or two to test this a bit.

FrankenWM uses keysyms for identifying keys, the ones you can see when using xev, which you might want to consider doing and comparing the results to qwerty-results. You should also be able to hardcode these keysyms in config.h, as XK_j and friends are just preprocessor macros.

[sulami]

So I have played around with Colemak and fail to find any issues. The way I tried it was by firing up a master build of FrankenWM with a default config in Xephyr and changing the keyboard layout inside using setxkbmap -variant colemak. I tested not all, but most of the hotkeys and everything seemd to work.

This means, if your problem persists, I would need a list of instructions to reproduce the issues.

[RoastPotatoes]

I had a go at using the master build of FrankenWM and still had the problem. I can't seem to tell what is causing this and why it is not all keys. I used setxkbmap -variant colemak but found this no different from the current method I was using. I set my layout via /etc/X11/xorg.conf.d/10-keyboard.conf

Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "us"
        Option "XkbModel" "pc104"
        Option "XkbVariant" "colemak"
EndSection

What else could I provide?

[sulami]

I am currently on the go, but I sat down today on my netbook and went through the entire config using us/pc104/colemak, to see if I can spot any pattern that can help us identify what is causing this. I would say, the results are pretty inconclusive.

[RoastPotatoes]

I still don't know what is causing the problem. But if I remove 10-keyboard.conf file and have setxkbmap us -variant colemak in my .xinitrc they seem to work. The strange thing is that there does not seem to be a difference in how the x keyboard is configured either way you set it. I used setxkbmap -print -verbose 10 and both methods provided the same output.

[sulami]

On Fri, Mar 27, 2015 at 08:19:28AM -0700, RoastPotatoes wrote:

I still don't know what is causing the problem. But if I remove 10-keyboard.conf file and have setxkbmap us -variant colemak in my .xinitrc they seem to work.

Hm, very interesting. Both of these settings should get loaded before FrankenWM, and should do the same thing. Well, at least we have a workaround.

Robin Schroer

[shmalebx9]

This isn't really a problem with Frankenwm. Global keyboard configuration is buggy. Frankenwm relies on X for keybinds. As long as the keyboard is set prior to Frankenwm everything should be good. Had the same issue with mmWM.