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

1.19: "closeOnExit": "always" does not work as expected #16110

Closed
237dmitry opened this issue Oct 6, 2023 · 3 comments
Closed

1.19: "closeOnExit": "always" does not work as expected #16110

237dmitry opened this issue Oct 6, 2023 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@237dmitry
Copy link

Windows Terminal version

1.19.2682.0

Windows build number

10.0.22621

Other Software

Any console app.

Steps to reproduce

Kill the application from outside. The tab or panel that the app was running in should automatically close. But that's not true.

Screenshot 2023-10-06 121252

Expected Behavior

Because closeOnExit is set to always, tabs or panels that have terminated applications should always be closed.

In 1.18 preview all worked fine

Actual Behavior

Tabs or panels do not close when the applications running in them are terminated by external commands or actions.
@237dmitry 237dmitry added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 6, 2023
@lhecker
Copy link
Member

lhecker commented Oct 6, 2023

Hey! We've recently already had a report for this issue at #16068. /dup #16068
It was fixed in #16090 and theoretically an update with this should ship next week or so if everything works out fine.

@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 labels Oct 6, 2023
@237dmitry
Copy link
Author

an update with this should ship next week or so if everything works out fine.

All will be fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. 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
@lhecker @237dmitry