starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Console]::Beep() does not activate "Bell Notifications" #21710

New Issue
Closed
opened 2026-01-31 07:52:47 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:52:47 +00:00
Owner
Copy Link

Originally created by @GarThor on GitHub (May 14, 2024).

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.

Originally created by @GarThor on GitHub (May 14, 2024). ### 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.
claunia added the Needs-TriageIssue-BugResolution-External labels 2026-01-31 07:52:47 +00:00
claunia commented 2026-01-31 07:52:48 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 14, 2024):

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 Beep as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹

@DHowett commented on GitHub (May 14, 2024): 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 `Beep` as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹
claunia commented 2026-01-31 07:52:48 +00:00
Author
Owner
Copy Link

@GarThor commented on GitHub (May 14, 2024):

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 Beep as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹

Bummer, I kinda figured it was something like that, but I figured it wouldn't hurt to ask.

@GarThor commented on GitHub (May 14, 2024): > 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 `Beep` as a direct call to PlaySound() (as of the last time I checked). There’s no way for us to intercept that. ☹ Bummer, I kinda figured it was something like that, but I figured it wouldn't hurt to ask.
claunia commented 2026-01-31 07:52:49 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 14, 2024):

I just checked the latest .NET code and it's still true today:
039d2ecb46/src/libraries/System.Console/src/System/ConsolePal.Windows.cs (L656-L673)

Because of this this bug unfortunately needs to be reported over at https://github.com/dotnet/runtime, if anything 😕.

@lhecker commented on GitHub (May 14, 2024): I just checked the latest .NET code and it's still true today: https://github.com/dotnet/runtime/blob/039d2ecb46687e89337d6d629c295687cfe226be/src/libraries/System.Console/src/System/ConsolePal.Windows.cs#L656-L673 Because of this this bug unfortunately needs to be reported over at https://github.com/dotnet/runtime, if anything 😕.
claunia commented 2026-01-31 07:52:49 +00:00
Author
Owner
Copy Link

@GarThor commented on GitHub (May 14, 2024):

I just checked the latest .NET code and it's still true today: 039d2ecb46/src/libraries/System.Console/src/System/ConsolePal.Windows.cs (L656-L673)

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.

@GarThor commented on GitHub (May 14, 2024): > I just checked the latest .NET code and it's still true today: https://github.com/dotnet/runtime/blob/039d2ecb46687e89337d6d629c295687cfe226be/src/libraries/System.Console/src/System/ConsolePal.Windows.cs#L656-L673 > > 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.
claunia commented 2026-01-31 07:52:49 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 14, 2024):

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 "`a" already (if you check out the other ConsolePal.*.cs files), so it IMO makes sense if Windows does too, even if it's only in the next big .NET version.
Maybe the best approach is to just make Beep() print "`a" while Beep(int, int) continues to use the kernel32 implementation.

@lhecker commented on GitHub (May 14, 2024): 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 ``"`a"`` already (if you check out the other `ConsolePal.*.cs` files), so it IMO makes sense if Windows does too, even if it's only in the next big .NET version. Maybe the best approach is to just make `Beep()` print ``"`a"`` while `Beep(int, int)` continues to use the kernel32 implementation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21710
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?