Move fast and break stuff, Windows Terminal style: Final update before release will nix your carefully crafted settings
(2020/04/23)
- Reference: 1587663009
- News link: https://www.theregister.co.uk/2020/04/23/windows_terminal_0_11/
- Source link:
The last major update for Windows Terminal prior to version 1.0 dropped last night but be warned: there are some breaking settings changes.
Microsoft's open-source Windows Terminal has come along in leaps and bounds since its first tentative steps last year. With (the now virtual) Build event due next month, users would be forgiven for expecting a non-preview release to crop up in the Microsoft store shortly.
However, the gang behind the project emitted one final major update last night, somewhat lunching the settings file. Program manager Kayla Cinnamon put it delicately, [1]posting : "We have made some changes to our settings that we'd like to bring to your attention..."
Senior project manager Rich Turner was a little more blunt.
Hey Windows Terminal fans - please read this post:
Terminal v0.11 includes breaking settings changes [2]https://t.co/hLVdcNzwb8 — Rich Tur-minal-ner-d (@richturn_ms) [3]April 22, 2020
And goodness, there are a lot of breaking changes to catch the unwary.
With version 1.0 looming, the team has indulged in a clear-out of deprecated settings from the .json file used by the app. The globals property is no longer supported and requestedTheme has been renamed to theme in the long list of settings changes.
We'd have to echo Cinnamon's advice: copy the existing settings file somewhere else, let Windows Terminal create a new one and then manually copy the settings back over.
It's irritating (especially if one has created scripts to generate the files) but this is preview code and stuff might break.
More potentially confusing is the renaming of the settings file (which will happen automatically) from profiles.json to settings.json . On the face of it, this is a logical move, if it were not for Visual Studio Code also using files called settings.json , which might initially confound some.
Cinnamon also stated that "Indexing in the Terminal starts at 0", a comment that could kick off a tab-versus-spaces-style spat between the "1 is the magic number" brigade and the "0 is the only true way" acolytes.
Settings updates and localisation support aside, the Windows Terminal looks to be nearly ready for release. Those expecting it in the Windows 10 May 2020 Update are in for a disappointment however – it will, for now, be sticking with the Microsoft Store. ®
Sponsored: [4]How to Build Your Digital Experience Portfolio
[1] https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release/
[2] https://t.co/hLVdcNzwb8
[3] https://twitter.com/richturn_ms/status/1253083493631844352?ref_src=twsrc%5Etfw
[4] https://go.theregister.co.uk/tl/1936/-8578/how-to-build-your-digital-experience-portfolio?td=wptl1936
Microsoft's open-source Windows Terminal has come along in leaps and bounds since its first tentative steps last year. With (the now virtual) Build event due next month, users would be forgiven for expecting a non-preview release to crop up in the Microsoft store shortly.
However, the gang behind the project emitted one final major update last night, somewhat lunching the settings file. Program manager Kayla Cinnamon put it delicately, [1]posting : "We have made some changes to our settings that we'd like to bring to your attention..."
Senior project manager Rich Turner was a little more blunt.
Hey Windows Terminal fans - please read this post:
Terminal v0.11 includes breaking settings changes [2]https://t.co/hLVdcNzwb8 — Rich Tur-minal-ner-d (@richturn_ms) [3]April 22, 2020
And goodness, there are a lot of breaking changes to catch the unwary.
With version 1.0 looming, the team has indulged in a clear-out of deprecated settings from the .json file used by the app. The globals property is no longer supported and requestedTheme has been renamed to theme in the long list of settings changes.
We'd have to echo Cinnamon's advice: copy the existing settings file somewhere else, let Windows Terminal create a new one and then manually copy the settings back over.
It's irritating (especially if one has created scripts to generate the files) but this is preview code and stuff might break.
More potentially confusing is the renaming of the settings file (which will happen automatically) from profiles.json to settings.json . On the face of it, this is a logical move, if it were not for Visual Studio Code also using files called settings.json , which might initially confound some.
Cinnamon also stated that "Indexing in the Terminal starts at 0", a comment that could kick off a tab-versus-spaces-style spat between the "1 is the magic number" brigade and the "0 is the only true way" acolytes.
Settings updates and localisation support aside, the Windows Terminal looks to be nearly ready for release. Those expecting it in the Windows 10 May 2020 Update are in for a disappointment however – it will, for now, be sticking with the Microsoft Store. ®
Sponsored: [4]How to Build Your Digital Experience Portfolio
[1] https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release/
[2] https://t.co/hLVdcNzwb8
[3] https://twitter.com/richturn_ms/status/1253083493631844352?ref_src=twsrc%5Etfw
[4] https://go.theregister.co.uk/tl/1936/-8578/how-to-build-your-digital-experience-portfolio?td=wptl1936