Skip to content

startingDirectory being invalid shouldn't cause silent failures #10225

@randomascii

Description

@randomascii

Windows Terminal version (or Windows build number)

1.8.1444.0

Other Software

No response

Steps to reproduce

Adjust the startingDirectory to the name of a directory that doesn't exist. Then launch Windows Terminal. That's it.

Expected Behavior

I was expecting an error message saying that the directory doesn't exist. This could be printed to the console or it could be a dialog. Ideally Windows Terminal would still launch since otherwise there is no clear way for me to fix this broken setting.

Actual Behavior

The Windows terminal window flashes and then closes. There is no indication of what the problem is and, unless you have memorized the path to the settings file, no way to fix the problem.

This issue can easily happen if you delete a directory or if you copy settings from one machine to another.

Metadata

Metadata

Assignees

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.Needs-Tag-FixDoesn't match tag requirementsProduct-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