-
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
doesn't work for a drive mounted to root / #42
Comments
Yes, this is a known issue, as One possible temporary workaround, until this is implemented, is to use the old way of configuring your setup using bind mounts. This kind of works, but leads to other problems in some situations, as discussed in #34 . I'll leave this issue open for now as a concise example for the |
I'd really like to see this work with I never compiled a Rust app before, but if you change the hard coded |
I just tried that and it works |
It would be nice if you could share your compiled Maybe providing two variants, one with |
If anyone needs to make it working, the 'easiest' way is to go through the installation of VS Tools 2018 + W10 SDK. I tried to use cargo+rust under WSL to generate a .exe but it's really tricky and complex to set up. And a build, and here you go, it works with a mount on root |
Great! Nice to hear that it works in principle. Note, however, that this could fail in some edge cases, e.g. if the output of some translated git command contains slashes that are not part of a path (but only few git commands are actually translated). I think many will find this useful, so I've added a new build with these changes (which are now in the I'm also closing this issue, as these changes seem to solve this specific use case. |
vscode output:
The text was updated successfully, but these errors were encountered: