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

There should be an error dialog for incorrect settings instead of just crashing #622

Closed
ThomasAunvik opened this issue May 9, 2019 · 4 comments · Fixed by #903
Closed
Assignees
Labels
Area-UserInterface Issues pertaining to the user interface of the Console or Terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. Severity-Crash Crashes are real bad news.

Comments

@ThomasAunvik
Copy link

ThomasAunvik commented May 9, 2019

Windows Build: 10.0.18362.86

Open Terminal.

Opened up settings, to profiles.json.

On a profile, for example cmd, added "icon": %windir%\\system32\\cmd.exe. Save.

On trying to focus on the terminal, it crashed. No errors. Almost instant crash.

Removed that line.

Tries to relaunch terminal, unable to launch it again.
Tried rebooting. Tried redeploying, did not work.

Edit: nvm, was just an extra comma in the end. It would launch again. But crashes when that exe is there.
i feel stupid for posting this issue without a second thought.

@zadjii-msft
Copy link
Member

Yea there's no way for us to get an image from an .exe at this time.

I'd recommend trying a .png, .jpg, or any other image format :)

@zadjii-msft
Copy link
Member

I am gonna take this issue as an opportunity to create a "there should be an error dialog for incorrect settings instead of just crashing" thread.

@zadjii-msft zadjii-msft changed the title Crashes on putting "Icon" to a .exe There should be an error dialog for incorrect settings instead of just crashing May 9, 2019
@zadjii-msft zadjii-msft self-assigned this May 9, 2019
@zadjii-msft zadjii-msft added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 9, 2019
@zadjii-msft zadjii-msft added this to the Windows Terminal v1.0 milestone May 9, 2019
@ThomasAunvik
Copy link
Author

Just noting, that the json files gets resaved as unformatted json when you use the app. Making it difficult to change your settings at the go.

@bitcrazed bitcrazed added Product-Terminal The new Windows Terminal. Severity-Crash Crashes are real bad news. labels May 16, 2019
@zadjii-msft zadjii-msft added the Area-UserInterface Issues pertaining to the user interface of the Console or Terminal label May 17, 2019
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label May 23, 2019
@zadjii-msft zadjii-msft added the Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. label May 23, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 23, 2019
@xa0082249956
Copy link

Windows Terminal crashed after I upgraded powershell-core from a old version to 7.0.0-preview.1.
This may because it cannot find the main shell. But I think it's better to "fall back" to cmd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-UserInterface Issues pertaining to the user interface of the Console or Terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. Severity-Crash Crashes are real bad news.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants