Open wbfw109 opened 3 weeks ago
Thanks for the detailed report!
This is coming from the design decision to stay in the current activated environment while moving around on the file system. But since the environment is activated automatically this doesn't sound like a good decision anymore.
I think we should rethink that behavior.
Checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pixi, using
pixi --version
. >> pixi 0.28.0Reproducible example
Environments
Projects
parent/pixi-py
pixi/examples/cpp-sdl
Directory Structure
parent ├── pixi-py └── pixi/examples/cpp-sdl
Steps to Reproduce
Navigate to the
cpp-sdl
directory frompixi-py
:In the terminal of the VS Code window for Project B, run the following command:
Issue description
Expected Output
will must output non-warning, but output is
🚨 pixi always uses the previous project's environment, so
pixi
commands don't make sense for Project B. F1 (> Reload Windows) in VS Code not affects the result..💡 Workaround
// 📅 2024-08-26 23:57:14 modified (; add details)
Add these into .vscode/settings.json in your pixi project.
and If you open the project in a new VS Code window (Ctrl+Shift+N) and run the command, no warning appears.
Expected behavior
No error and Warning.