-
Notifications
You must be signed in to change notification settings - Fork 10
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
The plugin is being blocked from opening by Apple #20
Comments
Same issue |
I found that Karabiner Elements solves the issue with Caps Lock. The most moronic part is that you have to "remap" Caps Lock to itself, and then the delay disappears. Unfortunately Caps Lock is still bugged / delayed at the login screen, since Karabiner element is only started after you login. |
I'd prefer not to use an app that logs my keystrokes - any possibility to do this via scripting? |
While a bit off topic, KE is open source, and afaik does not log keystrokes, and even if it did this would not be transmitted. What it does, however, as all such "tools", is listen to your keystrokes – this is a necessity in order to register the fact that E.g. Caps Lock was pressed. On PC this happens silently without the user knowing, but on Mac the program needs permission to do so. Check it out here: https://github.com/pqrs-org/Karabiner-Elements |
I'll post a fix for this issue in a few moments |
@gkpln3 Any progress on the fix? I see the same issue in macOS Sonoma 14.0. Your tool is our only hope in this crooked world for now 🙏 |
@gkpln3 Also experiencing this issue: M2 chip OS 13.5.1 (22G90) |
I wonder if, like Stretchly, you need to pass in |
@mathomp4 is right, the following works for me brew install --cask capslocknodelay --no-quarantine (MacBook Air M1, 2020) |
Description of the Issue
The plugin is now being blocked by Apple with the message "CapsLockNoDelay can't be opened because Apple cannot check it for malicious software" when you try to open the application file.
I could get past that following some of the tips detailed here but I remember that this wasn't happening before.
Is there anything to do, or it's just the result of the signing method?
Debug Information
MacOS Ventura 13.5 (22G74)
CapsLockNoDelay 1.0.8
The text was updated successfully, but these errors were encountered: