-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Windows Terminal may not open if profiles.json is corrupted #1499
Comments
IHMO an option like "restore defaults" would be great as well |
|
We are fairly sure we added a dialog for this... if you’re not seeing it, that’s pretty surprising. We have an issue tracking having a defaults file. #754 |
@DHowett what I really wanted to point out is to have a separate file with default values like we now have a |
Hi @DHowett I can confirm the dialog is popping up in some certain conditions. example: possible problems: current situation: suggestion: implement a button to reset the profile.json. in case it is corrupted there is no other way than Windows apps reset at the moment |
This'll be helped in part by #1348. The dialog should be working in all cases. Feel free to open a new issue if the dialog really isn't working. |
Agreed. |
Environment
Windows build number: Windows 10 1903
Windows Terminal version (if applicable): 0.2.1715.0
Any other software?
Steps to reproduce
edit profiles.json e.g. I tried to copy and paste some schemas from this templated
https://gist.github.com/mehulmpt/16826be279bb9bf70310b465ca9c5de3
After saving everything was fine and I really took care about not doing a mistake in the json formatting. However after closing and reopening Windows terminal
copy line 63 to 131 at the appropriate spot in profiles.json
https://gist.github.com/fcharlie/7530d36175bc5249f1ae92be536238cd
Expected behavior
The file should be checked for errors on startup of Windows Terminal. If there is an error it should fallback to a default config
also see #1404
Actual behavior
Windows Terminal does not start. no error message.
workaround
fully reset the app in app and features
The text was updated successfully, but these errors were encountered: