Skip to content
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

BEL sound should be customizable #9069

Closed
ARitz-Cracker opened this issue Feb 7, 2021 · 6 comments
Closed

BEL sound should be customizable #9069

ARitz-Cracker opened this issue Feb 7, 2021 · 6 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ARitz-Cracker
Copy link

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

@ARitz-Cracker ARitz-Cracker added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 7, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 7, 2021
@j4james
Copy link
Collaborator

j4james commented Feb 8, 2021

See issue #8366.

@ARitz-Cracker
Copy link
Author

See issue #8366.

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

@DHowett
Copy link
Member

DHowett commented Feb 8, 2021

/dup #8366

thanks all!

@ghost
Copy link

ghost commented 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 ghost closed this as completed Feb 8, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 8, 2021
@DHowett
Copy link
Member

DHowett commented Feb 8, 2021

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

@ghost
Copy link

ghost commented 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!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants