Timeline for Including virtual environment in bash prompt
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2019 at 6:43 | vote | accept | anki | ||
| Aug 23, 2019 at 5:55 | answer | added | nohillside♦ | timeline score: 0 | |
| Aug 22, 2019 at 20:07 | comment | added | anki | @nohillside But it is not in PS1 after modification. I want to see which env is active. See expected vs actual result. | |
| Aug 22, 2019 at 19:58 | comment | added | nohillside♦ | Not sure what you want. Doesn't conda set that automatically once you activate/create an environment? | |
| Aug 22, 2019 at 19:49 | history | edited | anki | CC BY-SA 4.0 |
added 197 characters in body
|
| Aug 22, 2019 at 19:41 | comment | added | anki | @nohillside Can I have the stored variable for the current active env in the bash_profile file somehow? and then add it to PS1? | |
| Aug 22, 2019 at 19:40 | comment | added | nohillside♦ | Virtual environments aren't a bash thing, no wonder you won't find anything in the man page. | |
| Aug 22, 2019 at 19:31 | history | asked | anki | CC BY-SA 4.0 |