Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't recognize the running shell. #106

Open
BZLLLLL opened this issue Jan 9, 2025 · 1 comment · May be fixed by #108
Open

Can't recognize the running shell. #106

BZLLLLL opened this issue Jan 9, 2025 · 1 comment · May be fixed by #108
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@BZLLLLL
Copy link

BZLLLLL commented Jan 9, 2025

I add fish at the last of my .bashrc to start fish under bash env.

When I click "Create Python Terminal", it sources .venv/bin/activate instead of .venv/bin/activate.fish.

How can I make it automatically use the correct activation script?
@BZLLLLL BZLLLLL changed the title Can't work in a different shell. Can't recognize the running shell. Jan 9, 2025
@karthiknadig
Copy link
Member

Currently we try to detect the shell type from the name of the terminal in VS Code. This is fragile. Cases like yours are not handled well in that scenario. Waiting on this API from VS Code to solve this: microsoft/vscode#230165

@karthiknadig karthiknadig added the bug Issue identified by VS Code Team member as probable bug label Jan 9, 2025
@karthiknadig karthiknadig linked a pull request Jan 9, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Better handling for venv activations karthiknadig/vscode-python-environments
2 participants
@karthiknadig @BZLLLLL