Terminal couldn't be opened if profile's commandline couldn't be opened (re-open) #2484
Labels
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
Environment
Steps to reproduce
still, like #1404
at the defualt profile, "commandline" can't be opened, terminal starts and right after it shuts down.
Make profile a mistake, like the image under.
After that, starting a windows terminal, terminal automatically closes without any message.
Expected behavior
Terminal shows up an error message like #2422
Actual behavior
Terminal doesn't show up any error message, just shuts down.
The text was updated successfully, but these errors were encountered: