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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi. I noticed that in
xonsh.prompt.env.env_name
(https://github.com/xonsh/xonsh/blob/0f16fa7d64859936560b2fc9dd60d8916ea8ba7c/xonsh/prompt/env.py) the function doc saysI am quite confused by such setting. Because when you create a virtualenv like this:
virtualenv --prompt myenv .venv
and activate it with
The env_name part of the prompt will naively becomes
myenv
without parentheses, which is quite ugly.Edit: I do notice vox, but still very confused on this issue.
Why does xonsh.prompt.env.env_name return
virtual_env_prompt
instead of_surround_env_name(found_envname)
? What is the design philosophy behind this?Beta Was this translation helpful? Give feedback.
All reactions