Use "default" system sound for terminal bell/beep, as opposed to "critical". #9110

Closed
opened 2026-01-31 01:46:17 +00:00 by claunia · 5 comments
Owner

Originally created by @sirocyl on GitHub (Jun 18, 2020).

I feel that the "Critical Stop" sound, also known as "SystemHand" or, as referenced here, SND_ALIAS_SYSTEMHAND, is too "critical"/high-priority of an audible feedback for a console beep - it plays out for too long and doesn't 'attack' as quickly as a neutral/default UI bell sound would.

As a counterexample, Ubuntu uses a low and quick hollow "thunk" sound. Mac has Sosumi, Funk, and so forth, for the Terminal beep.

I'd suggest replacing that in the Windows Terminal with SND_ALIAS_SYSTEMDEFAULT - the "Default Beep", as it's called in the Sound control panel.

(I'm not sure why Critical Stop was chosen here - if there is a persuasive reason (Human Interface Guidelines, for instance) then it's probably best to stay as such.)

I'll be making a PR which changes that one line, and I'll refer to this issue in the PR.

Usecases: cmd.exe, Ubuntu/WSL, rarely PowerShell.
ver is Microsoft Windows [Version 10.0.18363.900]
conhost.exe is as shipped, with latest Windows Updates installed - file/product version is 10.0.18362.1.

Originally created by @sirocyl on GitHub (Jun 18, 2020). I feel that the "Critical Stop" sound, also known as "SystemHand" or, as referenced [here](https://github.com/microsoft/terminal/blob/10bc1a6532d40d917c24956f97d5d08808bc7061/src/interactivity/win32/windowproc.cpp#L678), `SND_ALIAS_SYSTEMHAND`, is too "critical"/high-priority of an audible feedback for a console beep - it plays out for too long and doesn't 'attack' as quickly as a neutral/default UI bell sound would. As a counterexample, Ubuntu uses a low and quick hollow "thunk" sound. Mac has Sosumi, Funk, and so forth, for the Terminal beep. I'd suggest replacing that in the Windows Terminal with `SND_ALIAS_SYSTEMDEFAULT` - the "Default Beep", as it's called in the Sound control panel. (I'm not sure why Critical Stop was chosen here - if there is a persuasive reason (Human Interface Guidelines, for instance) then it's probably best to stay as such.) I'll be making a PR which changes that one line, and I'll refer to this issue in the PR. Usecases: cmd.exe, Ubuntu/WSL, rarely PowerShell. `ver` is `Microsoft Windows [Version 10.0.18363.900]` `conhost.exe` is as shipped, with latest Windows Updates installed - file/product version is `10.0.18362.1`.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:46:17 +00:00
Author
Owner

@DHowett commented on GitHub (Jun 18, 2020):

So, Terminal doesn't actually support the bell right now. The code you've identified is part of the vintage console host--and I'm not about to change how belling works in the vintage console host.

This will become meaningful when we do finally implement bell for Terminal: /dup #4046

@DHowett commented on GitHub (Jun 18, 2020): So, Terminal doesn't actually _support_ the bell right now. The code you've identified is part of the vintage console host--and I'm not about to change how belling works in the vintage console host. This will become meaningful when we _do_ finally implement bell for Terminal: /dup #4046
Author
Owner

@ghost commented on GitHub (Jun 18, 2020):

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!

@ghost commented on GitHub (Jun 18, 2020): 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!
Author
Owner

@DHowett commented on GitHub (Jun 18, 2020):

(I appreciate that you're working on a PR for this 😄 I just wanted to get out ahead of it!)

@DHowett commented on GitHub (Jun 18, 2020): (I appreciate that you're working on a PR for this :smile: I just wanted to get out ahead of it!)
Author
Owner

@sirocyl commented on GitHub (Jun 18, 2020):

Oof thanks for the quick respo <3

I'll drop that then, haha. Understood - here's to hoping, I'll thumb up the other issue, thanks!

I'll keep my own fork around, because maybe I'll try to build it and fix it on my own machine, heh.

@sirocyl commented on GitHub (Jun 18, 2020): Oof thanks for the quick respo <3 I'll drop that then, haha. Understood - here's to hoping, I'll thumb up the other issue, thanks! I'll keep my own fork around, because maybe I'll try to build it and fix it on my own machine, heh.
Author
Owner

@DHowett commented on GitHub (Jun 18, 2020):

👍

We offer no warranty for this, but if you want to replace conhost.exe (system32, subject to system file protection) with openconsole.exe built out of this repo. . . I can't stop you!

(it's the exact same code that gets built and packaged with Windows, it can just move a whole lot faster because it's out here in the open!)

@DHowett commented on GitHub (Jun 18, 2020): :+1: We offer no warranty for this, but if you want to replace _conhost.exe_ (system32, subject to system file protection) with _openconsole.exe_ built out of this repo. . . I can't stop you! _(it's the exact same code that gets built and packaged with Windows, it can just move a whole lot faster because it's out here in the open!)_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9110