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
Control + / (Slash) unconditional triggers the system alert sound on macOS #3014
Comments
Alacritty itself doesn't even have the ability to trigger the system alert sound, so this must be triggered by what you're running inside of Alacritty. Have you tried different terminals/shells? |
Yep, doesn't happen with Alacritty is using the visual bell (verified by Btw my mapping is:
which is
Both /cc @thaedal |
Have you tried a different shell too? iTerm uses zsh by default now, so if you're launching bash, that would explain the differences. Launching Alacritty from iTerm might also help troubleshoot this, just to check the environment matches up. |
Any updates? I have same issue. iTerm + Bash - silent |
+1 |
I chased this down to winit, and this hack seems to remove the beep without changing any other functionality: alexrenda/winit@7b1d49e (I'd imagine there's a more principled fix based on https://christiantietze.de/posts/2016/11/nsresponder-finding-beep/ and https://stackoverflow.com/questions/13519647/silence-cocoa-error-beep, but I don't enough experience with Cocoa to know the right way to fix this). |
Is this still an issue with the latest macOS version? |
The issue is still present for |
Have you tried 11? |
I don't have macos 11 at hand. Sorry |
I can confirm that the issue is present (and that the patch above fixes it) on macOS 11 |
BTW, the similar issue is present in standard macOS' Terminal.app too: Alternative terminal kitty also beeps but with effect (and |
Yes I am using MacOS Monterey v12.2.1 and Alacritty v0.10.1 |
I found this issue when looking to remove the beep for
|
Interesting, I still get the beep but the actions that are mapped to ctrl+/ now work also. I am on alacritty 0.10.1 (2844606) and macOS 12.3.1 |
I think it's actually coming from outside of Alacritty. I bound I can't find any trace of it in the keyboard settings or the Mac OS docs... What's it supposed to do? edit: and to clarify, I assume some apps prevent the key combination from "bubbling" up to the OS, so that's why I hear a bell in some windows but not others. |
Found this answer by @knoguchi over here:
|
Is anyone else having this issue again? The following code used to work but since I upgraded to 0.11.0 it works only until I hit
|
I have recently started having this problem again and the keybind to |
Actually no, the problem is still there. Looks like it's intermittent but I'm getting the system error sound when I type Control-/. |
Bumping this in hopes someone will see it. Trying to bind the same commenting action as on VSCode to terminal-run-(neo)vim but the annoying beep persists, despite the keystroke now working. |
A feasible workaround to avoid the alert sound when
It should take effect immediately. If not, reboot your device. It works on my side with macOS 13.4.1 and alacritty 0.12.2. Hope it is helpful. |
To anyone that have issue with Contro-/ on Alacritty and it's trying to configure a keybinding to it on TOML file. Check it out this link: #7608 (comment) |
Reproduced on macOS 10.11
I can map the keyboard shortcut just fine and it works as expected, but it will always (mapped or not) unconditionally trigger the system alert sound. Please note this is not some BELL character created by the shell as this would only cause the Alacritty window to flash.
Also reported Here.
The text was updated successfully, but these errors were encountered: