When I implemented the benchmarks in #86 then I realized how much slower it was to use interactive mode versus non-interactive. I'm using an ssh-agent so I have to use interactive mode.
But it is not all git commands that needs the ssh-agent, just those who access remotes (clone, fetch, pull and push afaik).
So I implemented a smart option for WSLGIT_USE_INTERACTIVE_SHELL that use interactive mode for just those commands.
And why not make it the default.
I also made wslgit share one environmental variable named WSLGIT to WSL which I use in my .bashrc to do the bare minimum of initialization for git to work.
My GUI tools that use wslgit feels a lot snappier now, and still use the ssh-agent for remote access :)
When I implemented the benchmarks in #86 then I realized how much slower it was to use interactive mode versus non-interactive. I'm using an ssh-agent so I have to use interactive mode.
But it is not all git commands that needs the ssh-agent, just those who access remotes (
clone
,fetch
,pull
andpush
afaik). So I implemented a smart option forWSLGIT_USE_INTERACTIVE_SHELL
that use interactive mode for just those commands. And why not make it the default.I also made
wslgit
share one environmental variable namedWSLGIT
to WSL which I use in my.bashrc
to do the bare minimum of initialization for git to work.My GUI tools that use
wslgit
feels a lot snappier now, and still use the ssh-agent for remote access :)