Some suggestions: Keycode binding, binding w/o mod key, etc

[ExperiBass]

Is your feature request related to a problem? Please describe. I stumbled across this in r/unixporn, and thought it would be a good experiment to see if i like it better than i3-gaps. But I'm noticing it lacks some features that i use daily.

• Keycode binding. I can use the name of the key given by xev -event keyboard, but having to type XF86KbdBacklight just feels unnecessary.
• Binding without mod key: Seems to exist already with _ but that isn't documented, so maybe I've stumbled across a bug?
• • Related: Can't seem to use super and shift together, another possible bug
• The config structure seems a bit unintuitive, something like bind SUPER+SHIFT+1 to action would be cleaner and easier to understand.

Just my two cents, other than these im enjoying it so far :D

Anything else?

[vaxerski]

Keycode: ok, can do.

no mod: leave it empty, it's not a bug. you can do

bind=,A,exec,amongus

and it will work without a mod. I think I mentioned it in the wiki or the example config, but I'm not sure.

super and shift together work for me, and everyone else, you must be doing something wrong.

bind=SUPERSHIFT,A,exec,amongus

should work.

binds are unintuitive? I'd say they aren't, you have the MOD field and the KEY field, what's wrong with that? Changing it right now will not happen, as that would break compat.

[ExperiBass]

super and shift together work for me, and everyone else, you must be doing something wrong.

bind=SUPERSHIFT,1,movetoworkspace,1 doesn't work for me, nor does bind=SUPERSHIFT,D,exec,i3-dmenu-desktop.

binds are unintuitive? I'd say they aren't, you have the MOD field and the KEY field, what's wrong with that?

my nitpick is i have difficulty picking apart statements unless theyre separated. i guess allowing whitespace in the config would help (bind = SUPER, 1, workspace, 1 instead of bind=SUPER,1,workspace,1).

[vaxerski]

I might allow whitespaces, that's doable.

if supershift doesn't work, is it captured by the wm? or does SUPERSHIFT+D print something into the window? (e.g. a terminal)

[ExperiBass]

if supershift doesn't work, is it captured by the wm? or does SUPERSHIFT+D print something into the window? (e.g. a terminal) it acts like the shift key isnt pressed at all, so it ends up just being SUPER+D, which i set to dmenu_run.

[vaxerski]

keyboard wack then, your shift has to be remapped / non-standard. use xev that i describe in the wiki and see what mask your shift key is, then use that mask instead (e.g. if shift is 256, and you want shift+alt, it'd be 264, because 256+8, cuz alt is 8)

[ExperiBass]

Now its just spitting out "0A" when i hit the binding...

[ExperiBass]

Its gotten weirder!

i can use SUPERSHIFT+F to fullscreen, but cant use that same binding for anything else.

[vaxerski]

maybe because you have 2 keybinds per supershift+f? i feel your system is haunted.

[ExperiBass]

maybe because you have 2 keybinds per supershift+f? i feel your system is haunted.

I'm starting to think that too xwx;

And I'm sure I don't have two, I cleared all the default keybinds and retyped them so I have a clean slate

[vaxerski]

SHIFT fixed in 1667180ac3554cdeaf00ac2cd0f3ad37e64bce30, my bad.

[vaxerski]

keycodes (keysyms) as ints added in b52e6ea0558193cbeb5978e220285a552fb4fc2c

[vaxerski]

Wiki updated to mention no MOD.

keycodes - done shift - fixed no mods wiki - updated config - no. spacing - I'll consider.

closing for now.