Skip to content

Make exit code behavior more disacoverable #10798

@superm1

Description

@superm1

Description of the new feature/enhancement

When a process exits with a return code while closing a terminal, the following message shows up (assuming exit 130)

[process exited with code 130]

It's difficult to know what this means, especially if it's while closing a pane. If a process returns an exit code that is non zero, I can't figure out how to get rid of that pane now. Example:
image

This inevitably leads eventually to #5214

Proposed technical implementation details (optional)

Add a clearer message why this happened, and how to change it.

Process exited with code 130, to adjust what happens with non-zero exit codes visit Settings->Foo->bar

Then in the GUI add a new option that will control adding

"closeOnExit": "always"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-UserInterfaceIssues pertaining to the user interface of the Console or TerminalIssue-TaskIt's a feature request, but it doesn't really need a major design.Product-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions