-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Console]::Beep() does not activate "Bell Notifications" #17263
Comments
Thanks for filing! Unfortunately (and I really do mean unfortunately - this bug makes me sad), the .NET runtime or the PowerShell console adapter actually implemented |
Bummer, I kinda figured it was something like that, but I figured it wouldn't hurt to ask. |
I just checked the latest .NET code and it's still true today: Because of this this bug unfortunately needs to be reported over at https://github.com/dotnet/runtime, if anything 😕. |
rad, thanks... I'll try over there. |
Thanks for filing it! I'm not familiar with .NET development, but as a terminal maintainer I do hope you have success. Other platforms use |
Windows Terminal version
1.19.11213.0
Windows build number
10.0.19045.0
Other Software
Powershell v5 and v7
I do have oh-my-posh installed, but I don't think that affects this behavior
Steps to reproduce
o Enable "Bell notificaiton styles" in "Advanced" for your powershell profile.
o Enter the command
[Console]::Beep()
into the console. Observe, while the terminal does emit an audible beep, it does not alert the user in any other way (via flashing the window or the taskbar as configured).Flashing/notifications do appear to be configurable when using the
Write-Host -NoNewLine "
a"` command however.Expected Behavior
[Console]::Beep() should respect the user's configuration for bell notifications.
Actual Behavior
[Console]::Beep() does not respect the user's configuration for bell notifications.
The text was updated successfully, but these errors were encountered: