On Windows, ~ expansion and shortened paths with backslashes now behave correctly.
What's wrong with this entry?
~ now expands only when it stands alone or is followed by the platform's own separator, and shortened paths that use backslashes are cut at a folder boundary instead of mid-name.
- Previously expansion keyed on
~/, which is not how a Windows path is written. - The shortening helper falls back to the last backslash when there is no forward slash in the path.
lastIndexOf("\\")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window