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.

Sign up for GitHub

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

Jump to bottom

A way to configure the bell sound #12235

Closed
rbanffy opened this issue Jan 24, 2022 · 2 comments
Closed

A way to configure the bell sound #12235

rbanffy opened this issue Jan 24, 2022 · 2 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

@rbanffy
Copy link

rbanffy commented Jan 24, 2022

Description of the new feature/enhancement

There doesn't seem to be a way to specify a sound for the terminal bell (ASCII 7). It'd be nice to specify one that's different from the system sound, which gets a bit confusing, as well as getting a different one as the default (so it's not as easy to confuse an Outlook warning to a terminal bell).

Proposed technical implementation details (optional)

A file selector should be added to the "Advanced" tab for each profile. Selecting a sound for a given profile would make that sound when an ASCII 7 character is output to the terminal.
@rbanffy rbanffy added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 24, 2022
@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 Jan 24, 2022
@zadjii-msft
Copy link
Member

You'll be happy to know this was added in #11511, which should be in 1.13.

/dup #8366

@ghost
Copy link

ghost commented Jan 24, 2022

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 Jan 24, 2022
@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 Jan 24, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rbanffy @zadjii-msft