Carl-Oskar Larsson

Simply adding a key with a lifetime (`-t life`) using `ssh-add.exe` shipped with Win32-OpenSSH fails: ```powershell > & 'C:\Program Files\OpenSSH\ssh-add.exe' -t 60 .\.ssh\id_ed25519 Enter passphrase for .\.ssh\id_ed25519: Could not add...

The problem is that `wslgit` always use the default wsl, so when accessing the filesystem from windows on another wsl instance the paths will translate to a Unix-path that exists...

If I remember correctly GitKraken use a built-in gitlib so wslgit unfortunately cannot help.

> > > I use SmartGit instead of GitKraken, which allows me to pick the `git` executable I want to use, so I second this feature request. > > If...

I have `wslgit.exe` (0.8.0-alpha-ish) renamed to `git.exe` in `%HOMEPATH%\bin` which I've added to the Windows Path. Both VSCode (stable) and SourceTree 3.2.6 picks up and use that git.  @charlwillia6...

Symlinks are 0 kB size, that is correct. But since you have the `resources` folder I guess that you cloned this repository? Easiest is to just download the latest release...

> > > @carlolars any idea for this maybe? To access mapped network drives they must be manually mounted inside WSL. `wslpath` cannot figure out that `T:` in your case...

> > > but T IS the WSL mount, how would I mount it inside of WSL? You can't.

Are there actually that many enviornment variables that are relevant? * `LANG`, `LC_*` - If any exists they should be passed to WSL. * `GIT_*` - If any exists then...

Something must have changed in uncrustify-0.71.0 that breaks this. Using `"uncrustify.useReplaceOption": true` works.