ColorTool: Add ps1xml as an accepted extension
#5.650 geöffnet am 29. Apr. 2020
Repository-Metriken
- Stars
- (35.764 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 27T 19h) (24 gemergte PRs in 30 T)
Beschreibung
Description of the new feature/enhancement
If you are using Windows Powershell, you'll discover that Windows Terminal changes it's default color scheme. However you are unable to change it back. This is due to a custom scheme extension which you can view in PowerShell ISE under Tools - Options. You can export the built-in themes but ColorTool won't allow you to use them. Per ColorTool doc, only json, .itermcolors, and ini file extensions are accepted. So add the option to read those files in, this may require cooperation with the PowerShell team. Ideally we'd be able to convert the color schemes to json so we can read them into Windows Terminal (ideally these should be added to defaults.json once we can export to json).
A clear and concise description of what the problem is that the new feature would solve.
Lets you continue to use the Windows PowerShell color themes if you enjoy using them.
Proposed technical implementation details (optional)
A clear and concise description of what you want to happen.
I want my Windows Powershell profile in WT to keep the same color scheme it originally had and/or change it to one of the other defaults listed in ISE.