-
Notifications
You must be signed in to change notification settings - Fork 59
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
Cannot handle path when working from WSL path in Windows #71
Comments
Yes, it would be nice to support these new paths. Right now, Adding support for these paths should be possible, e.g. by detecting and removing the prefix. |
+1 |
@andy-5 why don't you use |
Thanks for the suggestion (and good to know that it supports these paths). There is already some discussion on
|
It should be super simple to convert WSL2 UNC paths: just add/remove the Ideally, this would detect the UNC paths and also work with DrvFs or 9p mounts, so it'd work whether the git repo resides on the Windows side or the Linux side. |
I just released v0.9.0, which uses |
Not quite, I have a repo at
and when I go to it via CMD (which is T:\home\stan\projects\personal\WeakAuras2) and type
|
@carlolars any idea for this maybe? |
To access mapped network drives they must be manually mounted inside WSL. But unfortunately it seems to not be possible to, in WSL, mount a network drive that points to the WSL filesystem. I even tried to do a bind mount of the root filesystem to my I see that you actually use Power Shell and not cmd.exe. In PS you can actually do |
but T IS the WSL mount, how would I mount it inside of WSL? |
You can't. |
Yeah well for this cmd/ps example it does not really matter but I was mainly testing this way because it did not work in Fork either. |
The insider build for 1903 has a new functionality that allows browsing files on WSL from explorer. The paths look like
\\wsl$\Ubuntu\home\alecxvs\Git\myproject
.Running wslgit from this path gives this error:
thread 'main' panicked at 'Cannot handle path "\\\\wsl$\\Ubuntu\\home\\alecxvs\\Git\\myproject"', src\libcore\option.rs:1008:5
The text was updated successfully, but these errors were encountered: