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

About the default open question #3056

Closed
qaralotte opened this issue Oct 4, 2019 · 2 comments
Closed

About the default open question #3056

qaralotte opened this issue Oct 4, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@qaralotte
Copy link

qaralotte commented Oct 4, 2019

[Environment] Windows 10 1903 18362.356
1.In general, when I type 'cmd' in the address bar of a folder, cmd will switch the directory location to the location of the folder.However, if the open is 'wt', it is still the same, he still opens C:\Users\XXXX,even if I did not write the parameter ”startingDirectory“.
2.Even if I set the WSL ‘startingDirectory’ parameter on the terminal to the absolute location of a folder in the wsl root directory, he still opens the root directory of wsl.


If it is my parameters are not written, please advise
If it is a bug, please fix it as soon as possible.

@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 Oct 4, 2019
@zadjii-msft
Copy link
Member

Thanks for the bug report! Let me try and break each of these down:

  1. This is the same issue as Starting directory no longer respected #878. Unfortunately, if you have a startingDirectory set, you won't currently be able to use explorer to open the Windows Terminal in the current directory.
  2. This sounds quite a bit like Support linux paths for startingDirectory of WSL distros #592, though I could be misunderstanding. startingDirectory needs to be a Windows path, not a WSL path.

/dup #878
/dup #592

@ghost
Copy link

ghost commented Oct 4, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 4, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Oct 4, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants