Skip to content
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

virtualenv segment missing in HOME? #874

Closed
2 tasks done
Holt59 opened this issue Jul 29, 2021 · 4 comments · Fixed by #876
Closed
2 tasks done

virtualenv segment missing in HOME? #874

Holt59 opened this issue Jul 29, 2021 · 4 comments · Fixed by #876
Labels
🤩 enhancement Improvement of a feature

Comments

@Holt59
Copy link

Holt59 commented Jul 29, 2021

Prerequisites

  • I have read and understood the CONTRIBUTING guide
  • I have looked for duplicate issues before submitting this one

Description

When in the home folder, the Python segment is missing. I am using the following config for the Python segment:

{
    "type": "python",
    "style": "powerline",
    "powerline_symbol": "\uE0B0",
    "foreground": "#100e23",
    "background": "#906cff",
    "properties": {
        "prefix": " \uE235 ",
        "display_mode": "environment"
    }
},

Environment

  • Oh My Posh version: 3.169.2
  • Theme: gist
  • Operating System: Windows.
  • Shell: Powershell.
  • Terminal: Windows Terminal / VS Code terminal.

Optional

  • posh-git version: 1.0.0
  • git version: 2.29.2

Expected behavior: [What you expected to happen]

The Python segment symbol should be visible when in the home folder.

Actual behavior:

image

@JanDeDobbeleer
Copy link
Owner

@Holt59 that's actually by design. To always show the segment, you need to use "display_mode": "always" for the Python segment.

@Holt59
Copy link
Author

Holt59 commented Jul 31, 2021

@JanDeDobbeleer So there is now way to have the old v2 behavior? "display_mode": "always" shows the segment even when I'm not in a virtual environment, that's not what I want...

@JanDeDobbeleer
Copy link
Owner

@Holt59 we could do this differently, let me think about a different approach.

Copy link

github-actions bot commented Apr 8, 2024

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues.
If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🤩 enhancement Improvement of a feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants