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

Optionally play a sound when a long running command completes #15749

Closed
stravant opened this issue Jul 23, 2023 · 2 comments
Closed

Optionally play a sound when a long running command completes #15749

stravant opened this issue Jul 23, 2023 · 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

@stravant
Copy link

stravant commented Jul 23, 2023 •
edited
Loading

Description of the new feature/enhancement

Often developers need to run long running command line tasks such as builds, and would like to know when they've completed.

If the windows terminal could play a sound after completing a command which ran for longer than some configurable cutoff, such as a 60 seconds, it would provide a lot of value.

It's possible to create a shim program to use for this writing something like myCommand1 || myPlaySoundShim but that's too manual to actually be convenient in practice. A builtin for this would be much better.

This could be as simple as playing the existing BEL sound.
@stravant stravant added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 23, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 23, 2023
@zadjii-msft
Copy link
Member

Great idea! I think we're tracking some similar thoughts in #7955 - or, at least, I'm trying to agregate them there.

/dup #7955

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Jul 24, 2023
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
@stravant @zadjii-msft