-
-
Notifications
You must be signed in to change notification settings - Fork 845
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
caps_lock -> control or command depending on frontmost application #4042
Comments
This setting is working fine on my end. https://karabiner-elements.pqrs.org/docs/help/troubleshooting/breaking-changes/#modifiers |
Thanks, the modifier settings seem to be fine. Another possibility is that the device is excluded from Karabiner-Elements. Please take a look at the settings. |
While the remapping was in the "not working" condition, I used the Activity Monitor to force quit all Karabiner processes. They started themselves back up, and my remap started working again. At least I know how to work around this. Is there something I can/should enable to help further debug why it stops working? |
I have the exact same symptom of: My I tried the I also tried kill -9, got new PIDs but that didn't work either. NOTE: At some point I got to a state where the Karabiner menu's quit stopped quitting the app at all (as did Force Quit via activity monitor!) Some digging on previous issues & some GPT, I got this to finally work:
Although, ironically this didn't just stop karabiner, but got my hotkeys working. It must have just restarted! Luckily, all I wanted was for my bindings to work again :) BTW, as expected, after entering this "fixed" state via the 3 commands above the event viewer is functioning again. |
I have a very old complex modification that I've used for several years. It's still working for me on an M1 MacBook Pro running Monterey. On an M3 MacBook Air running Sequoia, works for a little while on Sequoia, but later stops until I reboot.
This is a shared laptop with multiple users logged in at the same time. That has been fine under older versions of macOS on different machines, but thought I'd mention it in case it's a factor.
When I say it stops, Caps Lock has no observable effect. It doesn't act as Control, Command, or even as Caps Lock. It's a no-op.
I've tried:
"hold_down_milliseconds": 100
but I'm not sure it applies in this usage. It didn't help the issue.My full modification is below.
Any help would be appreciated. I've tried searching other issues including closed ones, but haven't found the key yet.
I am very dependent on this muscle memory!
Thanks!
The text was updated successfully, but these errors were encountered: