Skip to content
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

WSL startingDirectory Problem #1183

Closed
SJang1 opened this issue Jun 9, 2019 · 2 comments
Closed

WSL startingDirectory Problem #1183

SJang1 opened this issue Jun 9, 2019 · 2 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@SJang1
Copy link

SJang1 commented Jun 9, 2019

Environment

Windows build number: Microsoft Windows [Version 10.0.18912.1001]
Windows Terminal version (if applicable): commit 2da5b0b

Steps to reproduce

Build a terminal, open WSL profile.

  1. If setting(profiles.json) has startingDirectory, erase it.
    At commit 2da5b0b, there is no startingDirectory for WSL

  2. Set "startingDirectory" : "%USERPROFILE%"

Expected behavior

Both WSL starts at home directory as user. (/home/username/)

Actual behavior

  1. if there is no startingDirectory, WSL starts at /mnt/c/WINDOWS/System32
  2. if startingDirectory is %USERPROFILE%, WSL starts at /mnt/c/Users/Windows-Username
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 9, 2019
@Summon528
Copy link
Contributor

Duplicate of #592. At the meantime, set startingDirectory to //wsl$/Ubuntu/home/username

@SJang1
Copy link
Author

SJang1 commented Jun 10, 2019

found that starting with "commandline" : "wsl.exe" make this problem, "commandline" : "ubuntu" does fine.

@SJang1 SJang1 closed this as completed Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants