Windows Terminal Preview v1.14.145 #13267
Replies: 6 comments 6 replies
-
|
Is |
Beta Was this translation helpful? Give feedback.
-
|
Which part of UTF-8 support are you looking for? #8000 is our big megathread tracking all unicode issues, so I'd start there. |
Beta Was this translation helpful? Give feedback.
-
|
Aha, 4 of 7 tasks |
Beta Was this translation helpful? Give feedback.
-
|
Oh no, I saw the version as 114514...... Sorry🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Are tabs rounded now 😍 ? |
Beta Was this translation helpful? Give feedback.
-
|
They've always been rounded on the tops, rounded on the bottom is tracked as an element in #3327 |
Beta Was this translation helpful? Give feedback.
-
|
I know it's a silly question... But: I use the preview version of the Microsoft Store. And I've noticed many times that there is a difference between the semantic versioning code of the release that is on GitHub, and the one that comes packaged for the store. But this time the difference caught my attention due to the coincidence of numbers.
Is there any logic in this definition? I even imagine that this question would be more directed to the team responsible for packaging for the Microsoft Store, but if I'm not mistaken, this is built into the project itself through CI/CD. |
Beta Was this translation helpful? Give feedback.
-
|
@DHowett We should have a doc that explains this madness. tl;dr - We have two slightly different packages we publish, a "windows 11" version (which actually relies on Framework Packages for dependencies, so it's a little smaller) and a "windows 10" version (which wholesale bundles them in our package, for folks who can't rely on FWP). We can't publish two versions to the store with the exact same build number, that won't do at all. So, to differentiate the "windows 11" version of the package from the "windows 10" version, we just change the last digit of the minor version. So we call the release |
Beta Was this translation helpful? Give feedback.
-
|
Well... Although it sounds a little crazy, as you said, it was the way they found to solve the problem, right? About the documentation explaining this... I see that it is indeed necessary! But maybe some adaptations or improvements can make this a little more self-explanatory, thus avoiding great efforts in the explanations. I don't know exactly where the "1" and "2" came from within this pattern, but I couldn't make any direct reference to the operating system versions (after all, Windows 11 is actually its version of the operating system 10.0.xxx). Well, it's just a crazy idea! Take it only if it makes any sense to you! Thank you for your patience in answering silly questions. |
Beta Was this translation helpful? Give feedback.
-
The
Man, that'd be great. We can't actually set the revision field of the package to anything other than |
Beta Was this translation helpful? Give feedback.
-
|
crashtastic, gonna build master and see if I can't debug it ... |
Beta Was this translation helpful? Give feedback.
-
|
In third paragraph above :: "Microsoft.VCLibs.UWPDesktop.140.00". Bad situation is that I, heretofore unaware of Windows Terminal, am troubleshooting installation failure of the .....8wekyb3d8bbwe.msixbundle file. |
Beta Was this translation helpful? Give feedback.
-
This release of Windows Terminal Preview, 1.14.145, was made generally available on the 26th of May, 2022.
It contains the following fixes, which are almost exclusively for bugs that we recalled 1.14.143 over!
As with prior releases, you need to install
Microsoft.VCLibs.UWPDesktop.140.00or make sure it is installed prior to installing Terminal. If you are using Terminal unpackaged, you will need to make sure you have the systemwide "Microsoft Visual C++ Redistributable" installed, and choose the Win10 version of our msixbundle. Yeah, it's strange!Bug Fixes
This discussion was created from the release Windows Terminal Preview v1.14.145.
Beta Was this translation helpful? Give feedback.
All reactions