-
Notifications
You must be signed in to change notification settings - Fork 1.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
VS Code adds to PS1 when it shouldn't #22882
Comments
@gabethehuman I have a few questions:
Please provide the debug logs which can help diagnose the issue:
Output for
|
Sure, I'll give you whatever info you need. This is my Details
And here is the output: Details
I also found a workaround for this issue that I'm ok with, I set |
Can you send a screenshot of how it looks in that case? Because it's a virtual environment, I expect the name of the virtual environment |
I see what it is, thanks for sharing your
which disables the prompt particularly for pyenv. If you notice in the logs, we use "~/.pyenv/versions/3.10.12/envs/yt/bin/activate" to activate pyenv instead of "pyenv activate yt", hence that variable is not respected. Can you add the following to your
|
If that doesn't work, please add This won't be needed once #22128 is fixed. |
It seems to work, thanks, I think the issue can be closed but I'll leave it to you to decide :) |
Great, thanks. Did adding that line to bashrc suffice or did you have to add it as systems variable? |
For me bashrc worked :) |
Okay cool. I'll keep an eye on how many users run into this, depending on which we can explore using "pyenv activate" commands instead, closing this issue for now. |
I have this annoying issue where VSCode adds stuff to my PS1. In this case I'm using pyenv, but it happens with conda as well.
system
is what should be in PS1, theyt
part is there only because I selected it in the bottom right corner in the Python extension.Any chance it's related to any of the issues in the main post?
Similar to @JoelFeiner-viimed I tried downgrading the extension or switching to the pre-release version, without any luck.
Originally posted by @gabethehuman in #22879 (comment)
The text was updated successfully, but these errors were encountered: