BEL sound should be customizable #12450

Closed
opened 2026-01-31 03:15:58 +00:00 by claunia · 6 comments
Owner

Originally created by @ARitz-Cracker on GitHub (Feb 7, 2021).

Description of the new feature/enhancement

I'm not sure who's idea it was to make the BEL "critical stop", but it was a terrible one. (I know, something something conpty something something beep.sys, either way, I acknowledge the reasons why things are the way they are)

I have custom sound schemes and hearing the "critical stop" sounds when I hold down backspace is annoying. It would be great if a path to a sound file could be specified, other than the binary enable/disable option

Originally created by @ARitz-Cracker on GitHub (Feb 7, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I'm not sure who's idea it was to make the BEL "critical stop", but it was a terrible one. (I know, something something conpty something something beep.sys, either way, I acknowledge the reasons why things are the way they are) I have custom sound schemes and hearing the "critical stop" sounds when I hold down backspace is annoying. It would be great if a path to a sound file could be specified, other than the binary enable/disable option
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:15:58 +00:00
Author
Owner

@j4james commented on GitHub (Feb 8, 2021):

See issue #8366.

@j4james commented on GitHub (Feb 8, 2021): See issue #8366.
Author
Owner

@ARitz-Cracker commented on GitHub (Feb 8, 2021):

See issue #8366.

My apologies! This didn't show up in my searches 😅

@ARitz-Cracker commented on GitHub (Feb 8, 2021): > See issue #8366. My apologies! This didn't show up in my searches 😅
Author
Owner

@DHowett commented on GitHub (Feb 8, 2021):

/dup #8366

thanks all!

@DHowett commented on GitHub (Feb 8, 2021): /dup #8366 thanks all!
Author
Owner

@ghost commented on GitHub (Feb 8, 2021):

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 (Feb 8, 2021): 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 (Feb 8, 2021):

Ugh. I typoed it, of course. It doesn’t mean anything in the backend, fortunately. :)

@DHowett commented on GitHub (Feb 8, 2021): Ugh. I typoed it, of course. It doesn’t mean anything in the backend, fortunately. :)
Author
Owner

@ghost commented on GitHub (Feb 8, 2021):

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 (Feb 8, 2021): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12450