fix git bash suggestions #248556
Merged
fix git bash suggestions #248556
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anthonykim1
reviewed
May 9, 2025
anthonykim1
approved these changes
May 9, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #245843
Initial investigation that led me to
shellIntegration.envas the cause:#248424 (comment)
From there, @anthonykim1 and I went back and forth on this to figure out the solution:
shellIntegration.env.value.PATHused to report the path using\correctly (in 1.98). Now, it uses/, so we are deferring toprocess.envto fix this, as that uses\and allows us to reolve the executables.Follow-up items, discovered during this lengthy debugging 😅 :
terminal.shellIntegration.env.value.PATHuses wrong separators forgit bash#248561 (@anthonykim1)