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

Prints "[process exited with code 9009]" instead of closing the Windows Terminal when I type "exit". #8172

Closed
Kerem00 opened this issue Nov 5, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Kerem00
Copy link

Kerem00 commented Nov 5, 2020

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.610]
Windows Terminal version (if applicable): 1.3.2651.0

Steps to reproduce

When you type something that is not recognized as a command and after that you type exit, it prints "[process exited with code 9009]" and doesn't close the Windows Terminal window.

SFdX1AAxKD

Expected behavior

If you type normal commands like cd or cls and after that you type exit, it closes the Windows Terminal window as expected.

LHoj3y7ucs

Actual behavior

exit command isn't closing the window.

@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 Nov 5, 2020
@zadjii-msft
Copy link
Member

Thanks for the report! Please make sure to search for duplicates when filing new issues. There's already a decent amount of discussion in the above issues explaining why this happens.

#4263 (comment)

This behavior exists to stop an error message printed out by a program from disappearing instantly when it exits. There is a class of applications for which that is extremely important. We're following this behavior because it is the right brhavior to follow, and because you can turn it off with a config option very easily.

#4736 (comment)

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.

@ghost
Copy link

ghost commented Nov 5, 2020

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 Nov 5, 2020
@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 Nov 5, 2020
@sinanca
Copy link

sinanca commented Feb 1, 2023

not working

[process exited with code 1 (0x00000001)]

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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