Garrett Campbell

@erikgrahn13 My intuition is that it's editing the PATH, but the VS Code environment itself isn't being changed. I've marked this as a bug and put in on our backlog....

Thank you for the feature idea. We may not be able to get to this immediately, but I'm tagging it for further discussion.

@yoavmil To help us investigate this, could you provide a small repro project so we could reproduce and investigate this issue? Thanks!

@bertbuchholz @yoavmil This issue should be fixed in the most recent official release, could you confirm and if it still reproduces, create a new issue? Closing this issue since it...

@yoavmil No, CMake Tools does not install cmake.exe or ninja.exe, you should either have Visual Studio installed and use a Visual Studio kit, or you should install the tools yourself....

@hwhsu1231 To confirm, there is no way to repro this on the command-line? It seems like if the issue is related to the `.bashrc` files, then I would expect that...

@hwhsu1231 However, it could have to do with our interpretation of the PATH variable while parsing the presets. I see you are using the pre-release version (THANK YOU!), does this...

@hwhsu1231 @Evelyn-001 Unfortunately this seems to be a difficult problem to reproduce in general. Either way, from all of your screenshots, this seems to be an issue of opening VS...

1. Specifically the `env` command for the `PATH` variable. 2. No, you don't need to ignore the CMake Tools extension, I just mean that if you directly print out the...

@aiyolo Does the above reproduction match the issue that you are hitting? Is it only this use case that it is happening in? Or is there more general issues?