-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unbind a layer modifier #2
Comments
I think something like this can fix the issue. - keyboards: [ "Some kbd"]
keymap:
capslock: reserved # noop
layers:
- modifiers: [ 'capslock' ]
keymap:
i: up
j: left
# etc...
|
My bad. Thanks! I was trying to bind it to
But your suggestion works! I'm however having some difficulty with replicating the Grave escape in QMK. Here's what I tried:
This almost works the way I want it to. Pressing grave on its own sends escape, pressing capslock+grave sends a backtick but pressing shift+grave also sends backtick while I would expect that to literally be shift+grave, i.e. tilde. Incidentally, I also tried pressing capslock+shift+grave (actually just pressing capslock+shift together is enough) and that crashed kbct.
Anyway, thanks for your help. |
Thanks, for the thorough explanation. Clearly this is a bug, will let you know when fixed. |
On an unrelated note, I've been using this for a few days now and it works well (apart from the bug above). So I'm thinking of archiving my project, are you ok with me linking to your project in the README? It only has 26 stars. |
Hi @arnarg. Yes, no problem! Happy to know that it was helpful. |
Hey, I wrote https://github.com/arnarg/waybind a while back and never found the time/interest to polish it up. I found your project and I'm trying it out to see if I can replace my tool. My original goal was to mimic my QMK 60% keyboards on my laptops so layers are perfect for this.
Anyway, I was trying this out and I use caps lock as a modifier for my layer and while testing kbct it still switches on caps lock when pressing it. Do you have an option of essentially making the key into a no-op when it's a modifier?
The text was updated successfully, but these errors were encountered: