You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows build number: Microsoft Windows [Version 10.0.18363.657]
Windows Terminal version (if applicable): 0.9.433.0
Any other software? not relevant
Steps to reproduce
open a new cmd shell in wt
type a command that doesn't work (e.g. foobarfoobar)
type exit
Expected behavior
wt tab/process should exit
Actual behavior
WT prints a message about exit code (e.g. [process exited with code 9009])
tab is "paused" as it no longer processes intput or output. wt can still be exited through the UI normally and continues to pump messages (so isn't "hung" in the technical sense).
Other Notes
This happens to me from time to time when exiting from wt. I've only seen it with cmd shell. I've seen it with various exit codes and other scenarios, but my above steps are the simplest to reproduce.
The text was updated successfully, but these errors were encountered:
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 27, 2020
Alas, this is a behavior that's highly conserved across multiple shells and terminal emulators on most mainstream operating systems; more info in #4223 (comment). If you'd rather it just exit every time, set closeOnExit to true. 😄 /dup #4223.
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
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 27, 2020
Environment
Steps to reproduce
open a new cmd shell in wt
type a command that doesn't work (e.g.
foobarfoobar
)type exit
Expected behavior
wt tab/process should exit
Actual behavior
WT prints a message about exit code (e.g.
[process exited with code 9009]
)tab is "paused" as it no longer processes intput or output. wt can still be exited through the UI normally and continues to pump messages (so isn't "hung" in the technical sense).
Other Notes
This happens to me from time to time when exiting from wt. I've only seen it with cmd shell. I've seen it with various exit codes and other scenarios, but my above steps are the simplest to reproduce.
The text was updated successfully, but these errors were encountered: