Use parameter expansion to fetch envs for envVarCollections in shellIntegration-bash.sh #245264
+6
−6
Conversation
This file contains 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
To fix issue ShellIntegration-bash is not properly escaping windows paths microsoft#245260 where echo is causing characters to be interpreted instead of escaped
|
Thanks for this. I agree, parameter expansion should be safer (since echo with special characters can cause some issues with those in windows path), and this would make things faster too since we avoid echo and cut (I think these spawn subprocesses) We also use the safer approach here with env reporting stuff. |
anthonykim1
approved these changes
Apr 2, 2025
anthonykim1
changed the title
|
@meganrogge can you test this one too when you're back? |
|
Free penel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To fix issue ShellIntegration-bash is not properly escaping windows paths #245260 where echo is causing characters to be interpreted instead of escaped.
#245260 issue mostly affects insider release at the moment