starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Getting problems with first line - upon first opening terminal & ANY PowerShell. #16346

New Issue
Closed
opened 2026-01-31 05:04:48 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 05:04:48 +00:00
Owner
Copy Link

Originally created by @RobFosterNYC on GitHub (Jan 6, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.0

Other Software

Using "Oh-My-Posh" customized Prompt.

Steps to reproduce

Just open Windows Terminal with customized prompt "Oh-My-Posh"

Expected Behavior

For icons to show on first line properly.

Actual Behavior

When opening the prompt each time, only the first line in the prompt is affected with some sort of glitch
that has vertical lines running through the "Oh-My-Posh" customized prompt.

Please refer to this post as it gives more details, when I posted it on PowerShell Github issues page.

https://github.com/PowerShell/PowerShell/issues/16690

Here is a reference picture of the problem.

Screenshot_90

Originally created by @RobFosterNYC on GitHub (Jan 6, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.0 ### Other Software Using "Oh-My-Posh" customized Prompt. ### Steps to reproduce Just open Windows Terminal with customized prompt "Oh-My-Posh" ### Expected Behavior For icons to show on first line properly. ### Actual Behavior When opening the prompt each time, only the first line in the prompt is affected with some sort of glitch that has vertical lines running through the "Oh-My-Posh" customized prompt. Please refer to this post as it gives more details, when I posted it on PowerShell Github issues page. https://github.com/PowerShell/PowerShell/issues/16690 Here is a reference picture of the problem. ![Screenshot_90](https://user-images.githubusercontent.com/18384135/148317596-78fe1e1c-eefc-4f28-a887-e9b5ddefbedb.jpg)
claunia added the Resolution-Duplicate label 2026-01-31 05:04:48 +00:00
claunia commented 2026-01-31 05:04:49 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Jan 6, 2022):

How does it look in the standard console host? Win+R --> pwsh -nol (with the same font to display the powerline correctly )
If it's the same then the problem is rather with oh-my-posh or maybe pwsh

@237dmitry commented on GitHub (Jan 6, 2022): How does it look in the standard console host? `Win+R` --> `pwsh -nol` (with the same font to display the powerline correctly ) If it's the same then the problem is rather with `oh-my-posh` or maybe `pwsh`
claunia commented 2026-01-31 05:04:49 +00:00
Author
Owner
Copy Link

@RobFosterNYC commented on GitHub (Jan 6, 2022):

You can see something breaking on the first line. Black lines going vertical just like the normal version.
.
Screenshot_95

@RobFosterNYC commented on GitHub (Jan 6, 2022): You can see something breaking on the first line. Black lines going vertical just like the normal version. . ![Screenshot_95](https://user-images.githubusercontent.com/18384135/148363844-5c484b5a-3f53-44de-96a1-4a8298c32031.jpg)
claunia commented 2026-01-31 05:04:49 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Jan 6, 2022):

So, this is not Windows Terminal. I would ask the oh-my-posh developers

@237dmitry commented on GitHub (Jan 6, 2022): So, this is not Windows Terminal. I would ask the [oh-my-posh](https://github.com/JanDeDobbeleer/oh-my-posh/issues) developers
claunia commented 2026-01-31 05:04:49 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 6, 2022):

This is a duplicate of #8341. Some users have reported that it's resolved by switching to WSL from the Microsoft Store - https://github.com/microsoft/terminal/issues/8341#issuecomment-940657032.

@j4james commented on GitHub (Jan 6, 2022): This is a duplicate of #8341. Some users have reported that it's resolved by switching to WSL from the Microsoft Store - https://github.com/microsoft/terminal/issues/8341#issuecomment-940657032.
claunia commented 2026-01-31 05:04:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 6, 2022):

/dup #8341

@zadjii-msft commented on GitHub (Jan 6, 2022): /dup #8341
claunia commented 2026-01-31 05:04:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 6, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 6, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 05:04:50 +00:00
Author
Owner
Copy Link

@RobFosterNYC commented on GitHub (Jan 6, 2022):

This is a duplicate of #8341. Some users have reported that it's resolved by switching to WSL from the Microsoft Store - #8341 (comment).

Aah, the new WSL is only for people running windows 11, not windows 10.
I have checked my Windows update and I currently have the latest update for WSL for my version of windows.

I did try the < Clear-Host > at the end of my $PROFILE file.
And that seems to work. Also this is not a Oh-My-Posh issue and some may believe. This is a Terminal Issue.
I was even told by PowerShell people that its also not them as well.

Hope this gets resolved in the new update or so.

@RobFosterNYC commented on GitHub (Jan 6, 2022): > This is a duplicate of #8341. Some users have reported that it's resolved by switching to WSL from the Microsoft Store - [#8341 (comment)](https://github.com/microsoft/terminal/issues/8341#issuecomment-940657032). Aah, the new WSL is only for people running windows 11, not windows 10. I have checked my Windows update and I currently have the latest update for WSL for my version of windows. I did try the < Clear-Host > at the end of my $PROFILE file. And that seems to work. Also this is not a Oh-My-Posh issue and some may believe. This is a Terminal Issue. I was even told by PowerShell people that its also not them as well. Hope this gets resolved in the new update or so.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16346
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?