➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2019-05-19 14:18 by lys.nikolaou, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg342855 - (view) | Author: Lysandros Nikolaou (lys.nikolaou) *  |
Date: 2019-05-19 14:18 | |
For those, who use custom tools for their terminals, prepending __VENV_PROMPT__ to PS1 doesn't really help all that much, because it gets overwritten by those tools. Would it make sense to export __VENV_PROMPT__ as an environment variable upon activation, so that these tools can make use of it, in order to edit PS1 accordingly? |
|||
| msg342856 - (view) | Author: Karthikeyan Singaravelan (xtreak) * |
Date: 2019-05-19 14:22 | |
Is this same as issue35328? |
|||
| msg342858 - (view) | Author: Lysandros Nikolaou (lys.nikolaou) * |
Date: 2019-05-19 14:25 | |
It is. Somehow search failed me big time. I'm closing the issue. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:15 | admin | set | github: 81147 |
| 2019-05-19 14:25:41 | xtreak | set | superseder: Set a environment variable for venv prompt |
| 2019-05-19 14:25:11 | lys.nikolaou | set | resolution: duplicate |
| 2019-05-19 14:25:01 | lys.nikolaou | set | status: open -> closed messages: + msg342858 stage: resolved |
| 2019-05-19 14:22:10 | xtreak | set | nosy:
+ xtreak messages: + msg342856 |
| 2019-05-19 14:18:39 | lys.nikolaou | create | |