starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Visual bell style should optionally affect the entire terminal pane #12195

New Issue
Closed
opened 2026-01-31 03:08:35 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 03:08:35 +00:00
Owner
Copy Link

Originally created by @lzybkr on GitHub (Jan 26, 2021).

In 1.6 - the visual bellStyle briefly displays a bell in the tab. I find this too subtle and easy to miss, especially when one's eyes are looking at the bottom of the terminal.

I'd originally envisioned a visible bell as briefly inverting the terminal - that would be hard to miss.

After experimenting with the shaders (and there is even a shader for inverting) - I think the visual bell feedback should be a customizable shader. Invert or even Retro could be good defaults, but I'm sure someone will come up with a really nice shader for a nice full window visual feedback effect.

Originally created by @lzybkr on GitHub (Jan 26, 2021). In 1.6 - the `visual` `bellStyle` briefly displays a bell in the tab. I find this too subtle and easy to miss, especially when one's eyes are looking at the bottom of the terminal. I'd originally envisioned a visible bell as briefly **inverting** the terminal - that would be hard to miss. After experimenting with the shaders (and there is even a shader for inverting) - I think the visual bell feedback should be a customizable shader. Invert or even Retro could be good defaults, but I'm sure someone will come up with a really nice shader for a nice full window visual feedback effect.
claunia added the Issue-TaskNeeds-Tag-FixProduct-TerminalArea-UserInterface labels 2026-01-31 03:08:36 +00:00
claunia commented 2026-01-31 03:08:37 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jan 26, 2021):

Are you expecting something that Git bash does in #8737 ? The "Visual Bell" effect?

@skyline75489 commented on GitHub (Jan 26, 2021): Are you expecting something that Git bash does in #8737 ? The "Visual Bell" effect?
claunia commented 2026-01-31 03:08:37 +00:00
Author
Owner
Copy Link

@lzybkr commented on GitHub (Jan 26, 2021):

I didn't realize there was an escape sequence for that and that it is now supported. That is certainly a reasonable choice, but that could be jarring too, which is why I suggested a configurable shader.

I do like the idea of applications just sending BEL and the terminal deciding how to notify the user rather than each tool needing configuration option to choose visual versus audible.

@lzybkr commented on GitHub (Jan 26, 2021): I didn't realize there was an escape sequence for that and that it is now supported. That is certainly a reasonable choice, but that could be jarring too, which is why I suggested a configurable shader. I do like the idea of applications just sending BEL and the terminal deciding how to notify the user rather than each tool needing configuration option to choose visual versus audible.
claunia commented 2026-01-31 03:08:37 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

I tend to agree. We can add more visual cues to the visual bell style.

@DHowett commented on GitHub (Jan 28, 2021): I tend to agree. We can add more visual cues to the visual bell style.
claunia commented 2026-01-31 03:08:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

Triaged into backlog. An enterprising youth could come along and add a cool visual effect if they wanted. 😄

@DHowett commented on GitHub (Jan 28, 2021): Triaged into backlog. An enterprising youth could come along and add a cool visual effect if they wanted. :smile:
claunia commented 2026-01-31 03:08:38 +00:00
Author
Owner
Copy Link

@garyo commented on GitHub (Mar 24, 2021):

Perhaps a different issue, but could we have a preference for the sound to play for the bell? Then we could have something less loud & intrusive, more bell-like, whatever.

@garyo commented on GitHub (Mar 24, 2021): Perhaps a different issue, but could we have a preference for the sound to play for the bell? Then we could have something less loud & intrusive, more bell-like, whatever.
claunia commented 2026-01-31 03:08:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 24, 2021):

@garyo you're looking for #8366

@zadjii-msft commented on GitHub (Mar 24, 2021): @garyo you're looking for #8366
claunia commented 2026-01-31 03:08:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2021):

You know, we did this in #9270

@zadjii-msft commented on GitHub (Aug 19, 2021): You know, we did this in #9270
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 Area-UserInterface Issue-Task Needs-Tag-Fix Product-Terminal
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#12195
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?