Option to choose terminal used for Git command

[imagoiq]

Hello,

I'm using WSL as default terminal for coding but it doesn't work very well with Git and Vscode. I'm using Git bash as a secondary terminal fot Git. It would be perfect if I can choose which terminal Gitlens uses for Git commands.

Thanks

[eamodio]

@imagoiq I'm pretty sure this would make for a pretty good first PR -- would you like to try?

[ganesh-4212]

Hi @eamodio, I'm interested to work on this issue.

[eamodio]

@ganesh-4212 awesome!

Here is a good place to start:
https://github.com/eamodio/vscode-gitlens/blob/master/src/views/viewCommands.ts#L716-L737

I believe window.createTerminal optionally takes shell command and args -- so we should be able to just have a couple new settings and pass them through

[kinzlee]

you can easily change the command that your vscode uses

[Ralonsogit]

Any update on this ?
Suddenly my Gitlens changed of default terminal, and now everytime Gitlens execute a command it does it with Powershell (which doesn't work as Powershell does not recognise the command git). Even if my default profile/shell is Git Bash. I don't know how to tell Gitlens to use Git bash.

I have already tried deprecated default shell user setting, and reinstalling Gitlens extension

[lisonge]

some problem

[davorpa]

Any update on this ?
Suddenly my Gitlens changed of default terminal, and now everytime Gitlens execute a command it does it with Powershell (which doesn't work as Powershell does not recognise the command git). Even if my default profile/shell is Git Bash. I don't know how to tell Gitlens to use Git bash.

I have already tried deprecated default shell user setting, and reinstalling Gitlens extension

Me too. I can't see any property to select launch like in git-graph

{
    // Specifies the path and filename of the Shell executable to be used by the Visual Studio Code Integrated Terminal, when it is opened by Git Graph.
    // For example, to use Git Bash on Windows this setting would commonly be set to "C:\Program Files\Git\bin\bash.exe".
    // If this setting is left blank, the default Shell is used.
    "git-graph.integratedTerminalShell": "C:\\Program Files\\Git\\bin\\bash.exe"
}

Default shell is managed using terminal.* properties

{
    // The Windows profiles to present when creating a new terminal via the terminal dropdown.
    // Set to null to exclude them, use the source property to use the default detected configuration.
    // Or, set the path and optional args.
    "terminal.integrated.profiles.windows": {
        "PowerShell": {
            "path": [
                "${env:windir}\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
                "${env:windir}\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
            ],
            "source": "PowerShell",
            "icon": "terminal-powershell",
            "args": ["-NoLogo", "-ExecutionPolicy", "Bypass"]
        },
        "Command Prompt": {
            "path": [
                "${env:windir}\\Sysnative\\cmd.exe",
                "${env:windir}\\System32\\cmd.exe"
            ],
            "args": [],
            "icon": "terminal-cmd"
        },
        "Git Bash": {
            "path": [
                "${env:ProgramW6432}\\Git\\git-bash.exe",
                "${env:ProgramFiles}\\Git\\git-bash.exe",
                "${env:ProgramFiles(x86)}\\Git\\git-bash.exe",
                "${env:ProgramW6432}\\Git\\bin\\bash.exe",
                "${env:ProgramFiles}\\Git\\bin\\bash.exe",
                "${env:ProgramFiles(x86)}\\Git\\bin\\bash.exe"
            ],
            "source": "Git Bash",
            "icon": "terminal-bash"
        }
    },
    "terminal.integrated.defaultProfile.windows": "Git Bash",
}

Been concrete... terminal.integrated.defaultProfile.windows, terminal.integrated.defaultProfile.linux or terminal.integrated.defaultProfile.osx attending to each OS platform

More about: https://code.visualstudio.com/docs/editor/integrated-terminal#_terminal-profiles

[andrew-atwood-infinitusai]

Also having this issue. I've set my default integrated terminal to run zsh via Rosetta (verified using the arch) command, as well as updating the git executable for VSCode internally to run through Rosetta so my hooks get executed appropriately, but GitLens seems to do its own thing and ignore everything. Some configuration for the shell that GitLens commands open is extremely necessary.

[carlin-q-scott]

I honestly removed this extension due to this issue. I cannot issue any git commands from gitlens while using WSL, and it tricks me into not using the built-in git history which works fine with WSL.

[flying-sheep]

My problem is that the Python extension injects source .venv/bin/activate into the terminal.

When GitLens opens its own terminal, that line is injected next to the git command, creating invalid syntax.

GitLens should really allow running commands outside of a terminal. Shell syntax is just too different to rely on things being inserted correctly.