-
Notifications
You must be signed in to change notification settings - Fork 37.3k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-profilesverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.76.2
- OS Version: Win11 22H2 (OS Build 22621.1344)
Steps to Reproduce:
- install Git for Windows SDK (without
Git for Windowsinstalled) - Open VSCode with
"terminal.integrated.defaultProfile.windows": "Git Bash"in vscodesettings.json - Open the vscode Terminal
- PowerShell opens (not Git Bash which is not listed either)
Potential fix:
Inside getGitBashPaths(), add some of these options:
- Add the default installation
c:\\git-sdk-64\\usr\\bin\\bash.exeas a special path - Add
${gitDir}\\usr\\bin\\bash.exewhen pushing togitBashPaths, so ifc:\\git-sdk-64\\usr\\binis in thePATH, findExecutable('git.exe') will addc:\\git-sdk-64as agitDirs, andc:\\git-sdk-64\\usr\\bin\\bash.exewill be pushed intogitBashPaths
Known workaround:
Create a link C:/Program Files/Git pointing to C:/git-sdk-64
# from git bash
# Assuming user with `SeCreateSymbolicLinkPrivilege` privilege (always true for admin users) and `export MSYS="winsymlinks:nativestrict $MSYS"` called in git bash
ln -s /c/git-sdk-64 /c/Program\ Files/Git
# or use NTFS Links
mklink /D "C:\Program Files\Git" "C:\git-sdk-64"Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-profilesverifiedVerification succeededVerification succeeded