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
Add support for audio bell #1528
Comments
Currently Alacritty does not provide any audio bell and it's not planned to add this in the near future. Judging if this is within scope or not is always tough since it might change based on demand (see scrollback which was initially not planned). However there already are a few issues which are related to this issue (see #1170 and #1072). Especially with #1072 I can see Alacritty supporting it in the future. |
Thanks for the swift reply! I can live with notifications via tmux, just wanted to make sure I'm not missing anything :-) |
Given the varying nature of the demands for this feature, and the constant doubt as to whether it's in scope — maybe shove it off onto the user and add a |
I like @Celti's suggestion |
I've included the bit of code from the top (playing a sound, even emiting a shell script to light up a small led-light on my desk just to test if an error was raised in tmux). while in iterm the sound sounds and the led on my desk flashes on. Alacritty seems to not even trigger the alert-bell hook in tmux. |
Interestingly, I came across this issue while using alacritty on Windows and wondering how to disable the audible bell. It's the default notification sound, and I was guessing it was generated by alacritty, but reading this it seems like it's probably coming from elsewhere. I'm using WSL bash. Any suggestions? |
Hmm... looks like the bell signal isn't even getting through to alacritty, since visual bell isn't working. It's probably being intercepted by WSL. |
I definitely don't get any audible bell under WSL. |
Adds a new configuration option under `visual_bell` called `bell_command` that reuses the command formatting of the keybindings. This allows for things like playing a notification sound. See alacritty#1528 (comment) Closes alacritty#1072
Adds a new configuration option under `visual_bell` called `bell_command` that reuses the command formatting of the keybindings. This allows for things like playing a notification sound. See alacritty#1528 (comment) Closes alacritty#1072
Adds a new configuration option under `visual_bell` called `bell_command` that reuses the command formatting of the keybindings. This allows for things like playing a notification sound. See alacritty#1528 (comment) Closes alacritty#1528
Adds a new configuration option under `visual_bell` called `bell_command` that reuses the command formatting of the keybindings. This allows for things like playing a notification sound. See alacritty#1528 (comment) Closes alacritty#1528
I am not sure this is the rightmost place to ask this, but I want to know if it is possible now to bind a sound to be played whenever user input is requested (for example, whenever a bunch of long-running commands finish and so the user is indicated of that)? Or should it be a shell's feature instead? |
Your shell can send |
Thanks, I'll try :) |
This worked for me on MacOS:
|
What bell program do we use for ArchLinux in 2023? I can't find the |
On Arch, Wayland does not have an accepted method of producing a system beep; use a media player app and a sound file. |
Thanks! Got it working now |
@francescoferraioli is this solution still working for you? [bell]
command = { program = "osascript", args = ["-e", "bell"] } is not working for me currently. |
Sorry, I've changed company since then and am no longer using a Mac so I'm not sure if it still works or not. |
It should be
|
Good spot, thank you! Not sure how I missed that but it's definitely working as expected now 🙂 |
Which operating system does the issue occur on?
macOS High Sierra v10.13.6
I don't get any audio notification for the terminal bell. The config file has options for
visual_bell
, but that's of no help when I'm looking at other fullscreen windows.For the time being, I've worked around the problem using tmux:
Does Alacritty not provide an audio bell? If not, is the feature planned or out of scope?
The text was updated successfully, but these errors were encountered: