-
Notifications
You must be signed in to change notification settings - Fork 177
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
Clarify the usage of Linux-style paths in 21H1 #455
Conversation
|
Docs Build status updates of commit f2460e6: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Hey @grische - Just another ping to ask that you sign the contributor agreement so I can merge your update into the live docs. If you prefer not to, I can make this update separately - your name just won't be listed as a contributor on the page. Thanks again for contributing! :) |
@mattwojo I am in the process of trying to get the CLA signed |
Sounds good. Thanks! Let me know if you get stuck on anything. |
Wait this might not be right - support for linux style paths was added in the Terminal, not Windows. microsoft/terminal#9223 |
@zadjii-msft - so it's incorrect to say: "Beginning in Windows 10 version 21H1" and we should instead say: "As of version 1.12.3472.0, the file systems of WSL distributions is directly referenced and does not need any prefix." >> Is this correct? It would still be accurate to state the rest below, yes? You can use {
"name": "Ubuntu-20.04",
"commandline" : "wsl -d Ubuntu-20.04",
"startingDirectory" : "/home/<Your Ubuntu Username>"
} |
Yep, that's right! |
Hello, I noticed the Terminal docs still has this "important" note: > [!IMPORTANT]
> On newer versions of Windows, `startingDirectory` can accept Linux-style paths. This is confusing because the rest of the text above that note was corrected in 7cd48bc to emphasize that it depends on the Terminal version, and not the Windows version. Also, 7cd48bc states that support for Linux-style paths was added in Terminal v1.12.3472.0, but it actually goes back to microsoft/terminal@a2a6050, which as GitHub shows us:
was first released in v1.11.2421.0 (Preview) and v1.11.2921.0 (Stable). |
For cross-reference purpose, here is the version-independent ID: "e76f9f11-cb0d-95be-7e04-8a9137252e2d" so that this PR appears in the "All page feedback" link in the live doc. |
@mattwojo would you be willing to review a PR that would clarify that? :) |
I clarified that in #516 |
No description provided.