You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If starship still displays the virtual env name, it must means the external starship binary is still being started with the old value. The behavior of (environment) variables in nushell can be non-intuitive. Please try reporting your issue upstream.
I think this might have been fixed by pypa/virtualenv#2422 but I am not a nu shell user so can't confirm. Is this still an issue with the most recent versions of nu shell and virtualenv activation script?
Bug Report
Current Behavior
Nushell can't hide
venv
afterhide-env VIRTUAL_ENV
.And while using virtualenv, after
deactivate
the Python version will display all time in this terminal tab.Expected Behavior
Hide
venv
afterhide-env VIRTUAL_ENV
Additional context/Screenshots
Possible Solution
Environment
Relevant Shell Configuration
Starship Configuration
# Your configuration here
The text was updated successfully, but these errors were encountered: