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.

Sign up for GitHub

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

Jump to bottom

code command does not work correctly only in WSL filesystem #36737

Closed
carpet92 opened this issue Oct 23, 2017 · 4 comments
Closed

code command does not work correctly only in WSL filesystem #36737

carpet92 opened this issue Oct 23, 2017 · 4 comments
Assignees
@Tyriar
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues workbench-os-integration Native OS integration issues WSL Issue when using WSL
Milestone
Backlog

Comments

@carpet92
Copy link

carpet92 commented Oct 23, 2017 •
edited
Loading

  • VSCode Version: 1.17.2
  • OS Version: Windows 10 Version: 1709 Build: 16299.19

Steps to Reproduce:

  1. Open WSL with bash or ubuntu command
  2. Go to "~"
  3. Then:
    • mkdir my-project
    • cd my-project
    • touch index.js
    • code .

After this steps, VSCode runs with all contents of Windows Desktop/ directory. But if I will run code . in any folder in Windows filesystem, for example in /mnt/c/Users/User/Desktop/my-project it opens VSCode correctly.

Reproduces without extensions: Yes
@vscodebot vscodebot bot added the workbench label Oct 23, 2017
@jeasonstudio
Copy link

This is my issue, #29812
I think vscode should greatly improve the support for wsl.

@carpet92 carpet92 reopened this Oct 23, 2017
@carpet92 carpet92 changed the title code command does not work correctly in WSL code command does not work correctly only in WSL filesystem Oct 23, 2017
@carpet92
Copy link
Author

Any ideas why it happens and how can we fix this?

@Tyriar
Copy link
Member

Tyriar commented Oct 30, 2017

Related: #32717

@bpasero bpasero added workbench-os-integration Native OS integration issues and removed workbench labels Nov 16, 2017
@bpasero bpasero assigned joaomoreno and unassigned sandy081 Nov 16, 2017
@joaomoreno joaomoreno removed their assignment Nov 17, 2017
@joaomoreno joaomoreno added windows VS Code on Windows issues WSL Issue when using WSL labels Nov 17, 2017
@joaomoreno joaomoreno added this to the Backlog milestone Nov 17, 2017
@Tyriar Tyriar added the bug Issue identified by VS Code Team member as probable bug label Dec 15, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 28, 2017

Duplicate #13138

@Tyriar Tyriar closed this as completed Dec 28, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 28, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues workbench-os-integration Native OS integration issues WSL Issue when using WSL
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@joaomoreno @bpasero @Tyriar @sandy081 @jeasonstudio @carpet92