Right now the script uses powershell.exe even if user is using pwsh.exe which can lead to multiple side-effects. This PR fixes it by taking the name of the current process.
Also added a warning in the README to use the right shell.
Another fix is to make sure .ssh folder exists in home folder, otherwise user will see the following error:
2021/07/13 22:55:09 socat[406] E bind(5, {AF=1 "/home/username/.ssh/agent.sock"}, 34): No such file or directory
lucyllewy
commented
3 years ago
Right now the script uses
powershell.exeeven if user is usingpwsh.exewhich can lead to multiple side-effects. This PR fixes it by taking the name of the current process. Also added a warning in the README to use the right shell.Another fix is to make sure
.sshfolder exists in home folder, otherwise user will see the following error: