Make a setting to disable the bell. This could be a per profile setting.
Maybe other "bell" settings can be desirable like:
"bell": "enable" (default)
"bell": "disable" (this feature request)
"bell": "visual"
So with that in mind don't let the setting be a boolean.
Probably related to #72
This depends on #1608.
In addition, I want that to be configurable on both global and on profile level
One change though, instead of the following to be default
"bell": "enable"
use
"bell": "default"
that way we can use
"bell": "path to mp3,wav,ogg"
I'm gonna merge this with "the terminal should actually support bell", because right now it actually _doesn't even support bells._
/dup #4046
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Hey with #7679 adding support for audible bells, let's re-open this to track disabling them (again)
Since this issue is reopened, will this get the same milestone as #7679?
@ffes Absolutely, I'll make sure of that 鈽猴笍
Note to self: we should do this as an enum like:
"bellStyle": "audible"|"visible"|"none"
We don't need to implement visible right now, but we should do it this way so we're future-proof
:tada:This issue was addressed in #7793, which has now been successfully released as Windows Terminal Preview v1.5.3142.0.:tada:
Handy links:
I'm on the Windows Terminal Preview from the Microsoft Store, and while I can't determine if the bell is truly disabled for a Powershell shell, I am definitely hearing it while in Alpine WSL.
Here's what I have in my settings.json (which I allowed Terminal to recreate after installing the newest 1.5 release):
...
"bellStyle": "none",
...
I'll note that VS Code was unable to see any "bell" properties (I assume these properties are populated from the json schema).
I have other features from 1.5 like a maximizedFocus so I'm positive I have the most recent version. Should I do a full uninstall and then install Terminal Preview fresh?
Where did you put bellStyle? In the global settings (at the root of the json), or in a profile? Since bellStyle is a per-profile setting, if you want it to apply to all profiles, you'll need to put it in the profiles.defaults object:

Excellent call! Indeed, that fixes it. Thanks!