Skip to content

Instantly share code, notes, and snippets.

@xqm32
Last active February 20, 2024 05:42
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save xqm32/df541525ed6d849e5736562282ba6b47 to your computer and use it in GitHub Desktop.
Save xqm32/df541525ed6d849e5736562282ba6b47 to your computer and use it in GitHub Desktop.
VS Code Bugs

[Python] Unexpected virtual environment activating microsoft/vscode#180486

For workspace like:

.
├── AandB.code-workspace
├── DirA
│  ├── A.py
│  └── venvA
└── DirB
   ├── B.py
   └── venvB

Open A.py and press Ctrl+`, the terminal is created at DirA and automatically activates venvA. That's what we expect VS Code to do. However, open B.py and press Ctrl+`, the terminal is created at DirB but activates venvA, not venvB!, That's not what we expect. If we press Ctrl+Shift+`, and select DirB, VS Code will activate venvB in terminal, which is what we want when open B.py and press Ctrl+`.

[Git] Symbol link files's status is not either NEW or UPDATE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment