-
Notifications
You must be signed in to change notification settings - Fork 0
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
Detect and scan WSL roots and other remotes #4
Comments
I made a few tests on WSL : if the Lines 37 to 44 in b975052
It only shows WSL repositories, but that's what I expect as a WSL vscode user :
Hope it helps :) |
That totally makes sense. I think, we should prefer
On the other hand, combining these two automatically is still a problem which I think we should not solve because these two are different environments and filesystems with very minimal APIs support. Even if I implement that, it will be slow and buggy. The primary reason I created repo and this extension was speed. |
Yep, looks good to me ! An improvement for later on the WSL flow could be to have a vscode command to download the repo unix binary to a known location so we won't have to download it our-self or set the PATH. |
I've just published v0.4.0 which includes —
|
See #2
As of now, WSL2 does not provide any reliable way to retrieve home directories and even if we add them manually, traversal is really slow from Windows.
The text was updated successfully, but these errors were encountered: