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

[WSL2] Oh My Posh Themes broken on new tab startup #16527

New Issue
Open
opened 2026-01-31 05:14:48 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:14:48 +00:00
Owner
Copy Link

Originally created by @IsaacLf on GitHub (Jan 28, 2022).

Windows Terminal version

Windows Terminal Preview Version: 1.12.3472.0

Windows build number

19043.1469

Other Software

  • on-my-posh v7.5.1 (in WSL2, Ubuntu 20.04)
  • CaskaydiaCove NF (Cascadia Code Nerd Font) installed on Windows

Steps to reproduce

Once you configured your bash with Oh-My-Posh theme (the theme I'm using is: powerlevel10k_rainbow) and your Nerd Font.

  1. Open a new instance of Windows Terminal or a new tab of WSL2 (Ubuntu in this case).

Expected Behavior

  1. The terminal should render the theme correctly, from startup:
    image

As example, in vscode terminal, when you open a new WSL terminal, will load correctly (that's the expected behavior from Windows Terminal as well):
image

Actual Behavior

  1. The terminal shows broken (not as expected), as following:
    image

You can clear the console with clear command and the console will look as expected, but it's broken from startup (new terminal instance or new tab)

Originally created by @IsaacLf on GitHub (Jan 28, 2022). ### Windows Terminal version Windows Terminal Preview Version: 1.12.3472.0 ### Windows build number 19043.1469 ### Other Software - on-my-posh v7.5.1 (in WSL2, Ubuntu 20.04) - CaskaydiaCove NF (Cascadia Code Nerd Font) installed on Windows ### Steps to reproduce Once you configured your bash with Oh-My-Posh theme (the theme I'm using is: `powerlevel10k_rainbow`) and your Nerd Font. 1. Open a new instance of Windows Terminal or a new tab of WSL2 (Ubuntu in this case). ### Expected Behavior 1. The terminal should render the theme correctly, from startup: ![image](https://user-images.githubusercontent.com/36938997/151510178-d1d62635-f888-4ccd-aa4e-bb70c5a8a47f.png) As example, in vscode terminal, when you open a new WSL terminal, will load correctly (that's the expected behavior from Windows Terminal as well): ![image](https://user-images.githubusercontent.com/36938997/151510423-86132f2c-917b-4507-9cb5-776ef3fc289a.png) ### Actual Behavior 1. The terminal shows _broken_ (not as expected), as following: ![image](https://user-images.githubusercontent.com/36938997/151509945-3437384d-93b6-43c1-881e-371a30ea1419.png) You can clear the console with `clear` command and the console will look as expected, but it's broken from startup (new terminal instance or new tab)
claunia added the Resolution-Duplicate label 2026-01-31 05:14:48 +00:00
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#16527
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?