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

Segment after newline is not displayed with Version 3.75.1 #354

Closed
2 tasks done
MJECloud opened this issue Jan 17, 2021 · 5 comments
Closed
2 tasks done

Segment after newline is not displayed with Version 3.75.1 #354

MJECloud opened this issue Jan 17, 2021 · 5 comments

Comments

@MJECloud
Copy link
Contributor

MJECloud commented Jan 17, 2021

Prerequisites

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

Description

With version 3.75.1 the new line segment is not displayed in powershell.

Environment

  • Oh my Posh version: 3.75.1
  • Theme: my own theme but also tested with the powerlevel10k_classic
  • Operating System: Windows
  • Shell: PowerShell 7.1.1
  • Terminal: WindowsTerminal

Steps to Reproduce

  1. Update oh-my-posh to Version 3.75.1
  2. Set a theme with a "newline"

Expected behavior: [What you expected to happen]
image
image

Actual behavior: [What actually happened]
image
image

@MJECloud MJECloud changed the title New line is not displayed with Version 3.75.1 "New line"-segment is not displayed with Version 3.75.1 Jan 17, 2021
@MJECloud MJECloud changed the title "New line"-segment is not displayed with Version 3.75.1 Segment after newline is not displayed with Version 3.75.1 Jan 17, 2021
@JanDeDobbeleer
Copy link
Owner

I think I know what went wrong. Will fix tomorrow 🙏🏻

@JanDeDobbeleer
Copy link
Owner

JanDeDobbeleer commented Jan 18, 2021

I could reproduce it, this change resolves the issue.

@bgelens
Copy link
Contributor

bgelens commented Jan 18, 2021

Can confirm the fix on my end! Thanks @JanDeDobbeleer

@MJECloud
Copy link
Contributor Author

It works, thank you @JanDeDobbeleer!

Copy link

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 May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants