You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, ~ paths are resolved to Linux user directories.
E.g. vim ~/.ssh/config is actually (Linux) vim /home/$USER/.ssh/config rather than (Windows) vim $env:USERNAME/.ssh/config
Describe the solution you'd like
A clear and concise description of what you want to happen.
Using tildes ~ should resolve to the Windows user directory.
Describe alternatives you've considered
As a quick patch, add the following line to WslInterop.psm1, within the for loop of path argument translation, as the last instruction of the for loop:
if (`$args[`$i].StartsWith("~")) {
`$args[`$i] =`$args[`$i] -replace"^~","/mnt/c/Users/`$env:USERNAME"
}
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, ~ paths are resolved to Linux user directories.
E.g.
vim ~/.ssh/config
is actually (Linux)vim /home/$USER/.ssh/config
rather than (Windows)vim $env:USERNAME/.ssh/config
Describe the solution you'd like
A clear and concise description of what you want to happen.
Using tildes ~ should resolve to the Windows user directory.
Describe alternatives you've considered
As a quick patch, add the following line to
WslInterop.psm1
, within the for loop of path argument translation, as the last instruction of the for loop:Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: