-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Feature Request: disable bell #2360
Comments
This depends on #1608. |
In addition, I want that to be configurable on both One change though, instead of the following to be default
use
that way we can use
|
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:
We don't need to implement |
This commit makes the Windows Terminal play an audible sound when the `BEL` control character is output. The `BEL` control was already being forwarded through conpty, so it was just a matter of hooking up the `WarningBell` dispatch method to actually play a sound. I've used the `PlaySound` API to output the sound configured for the "Critical Stop" system event (aka _SystemHand_), since that is the sound used in conhost. ## Validation I've manually confirmed that the terminal produces the expected sound when executing `echo ^G` in a cmd shell, or `printf "\a"` in a WSL bash shell. References: * There is a separate issue (#1608) to deal with configuring the `BEL` to trigger visual forms of notification. * There is also an issue (#2360) requesting an option to disable the `BEL`. Closes #4046
Adds a new setting, `bellStyle`, to be able to disable the audible bell added in #7679. Currently, this setting accepts two values: * `audible`: play a noise on a bell * `none`: Don't play a noise. In the future, we can add a `"bellStyle": "visible"` for flashing the Terminal instead of making a noise on bell. ## Validation Steps Performed Pressing <kbd>Ctrl+G</kbd> in cmd, and hitting enter is an easy way of triggering a bell. I set the setting to `none`, and presto, the bell stopped. Closes #2360
🎉This issue was addressed in #7793, which has now been successfully released as 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):
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? |
Excellent call! Indeed, that fixes it. Thanks! |
Description of the new feature/enhancement
Make a setting to disable the bell. This could be a per profile setting.
Maybe other "bell" settings can be desirable like:
So with that in mind don't let the setting be a boolean.
Probably related to #72
The text was updated successfully, but these errors were encountered: