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.

Sign up for GitHub

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

Jump to bottom

Terminal couldn't be opened if default profile can't be opened. #1404

Closed
SJang1 opened this issue Jun 22, 2019 · 2 comments
Closed

Terminal couldn't be opened if default profile can't be opened. #1404

SJang1 opened this issue Jun 22, 2019 · 2 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@SJang1
Copy link

SJang1 commented Jun 22, 2019 •
edited
Loading

What's Happening?

When (somehow) which "defaultProfile" is not able to run like miss-typing "commandline" goes like "powershell.ex" (no e) so there is no program to run it, windows terminal just shuts down when opening terminal, (or not the command line program, like office program WINWORD.EXE => opens word program and terminal shuts down.) and never can be opened before finding profiles.json and change wrong thing manually or change defaultProfile to which it can be run on windows terminal.

Proposed technical implementation details

So, If something that (Cannot use Windows terminal because of profiles.json) happens, Opening a popup "Can't load Terminal" with button open profiles.json before Windows Terminal shuts down like the image
image

or just not load any kind of commandline and make a select screen which profile to load for user like this image
image

BTW I just made image using mspaint
@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 Jun 22, 2019
@SJang1
Copy link
Author

SJang1 commented Jun 22, 2019 •
edited
Loading

...or not closing windows terminal if all tabs are closed and show up select screen like second one could be great too. This even can fix the problem.

@Karl-WE Karl-WE mentioned this issue Jun 23, 2019
Closed
@DHowett-MSFT
Copy link
Contributor

Most of this is a duplicate of #1348.

@DHowett-MSFT DHowett-MSFT added Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 24, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 24, 2019
@SJang1 SJang1 mentioned this issue Aug 20, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @SJang1