-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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.
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
pyenv virtual env does not show until activate is run #2791
Comments
That |
And no, it's not possible the name of the virtual environment before you activate it. |
But the environment is already activated, I just did not run activate again after opening the terminal. I'm not a python pro. However, I wonder if I have to manually (re)activate every time, how really helpful is showing the label. I mean, I would expect to rely on that label to know if I'm in the right virtualenv to know if I need to activate a different one or not, right? |
Virtual environment is a property of a shell. When you activate it in one shell, it does not become active in another shell. When you open a terminal, it starts a new shell. The virtual environment isn't active there. |
Actually I was wrong but my request still stands. I'm using VS Code, when a virtualenv is chosen on VS Code it automatically activates a virtualevn when the shell is open, but p10k does not show see below: but that was solved by setting:
Thank you for the responsivity <3 |
I'm not sure I understand your last comment. Are you saying the issue is now resolved or is something not working as you expect? |
Try this: #1430 (comment) |
Firstly thank you for all the great work put on p10k, I absolutely love it!
I'm wondering why I cannot see my pyenv when I open my terminal but only after I activate a virtualenv, see image below. Is there any way I could show it as soon as a terminal is open?
Here's my flags from running:
Flags
The text was updated successfully, but these errors were encountered: