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

With fragments extension, refer an icon/asset from another appx. (reference: ubuntu WSL icon) #16800

New Issue
Closed
opened 2026-01-31 05:23:07 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:23:07 +00:00
Owner
Copy Link

Originally created by @didrocks on GitHub (Feb 17, 2022).

Description of the new feature/enhancement

As part of customizing the Ubuntu autogenerated WSL profile via fragments, we want to be able to replace the default tux icon by our Ubuntu one.

However, we don’t really know where this assets will be placed on disk and when using ms-appx:/// schema, it logically refers to Windows Terminal itself and not the WSL appx.

We can’t really use \wsl$\ either as it’s only available once the WSL VM is active.

Is there any hint on how this could be done with the current code or do you need to develop something for this?

Proposed technical implementation details

We can imagine that if Windows Terminal knows from which appx a fragment is coming, then ms-appx:/// might refer to it.

Other informations

A similar issue will occur with fonts: ideally, the font shipped from the WSL package (like our ubuntu fonts) would be easily referenced. However, we can’t make it a sharedFonts, as there are multiple ubuntu applications in the store for different versions, which would conflict system-wide.

Originally created by @didrocks on GitHub (Feb 17, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement As part of customizing the Ubuntu autogenerated WSL profile via fragments, we want to be able to replace the default tux icon by our Ubuntu one. However, we don’t really know where this assets will be placed on disk and when using ms-appx:/// schema, it logically refers to Windows Terminal itself and not the WSL appx. We can’t really use \\wsl$\ either as it’s only available once the WSL VM is active. Is there any hint on how this could be done with the current code or do you need to develop something for this? # Proposed technical implementation details We can imagine that if Windows Terminal knows from which appx a fragment is coming, then ms-appx:/// might refer to it. # Other informations A similar issue will occur with fonts: ideally, the font shipped from the WSL package (like our ubuntu fonts) would be easily referenced. However, we can’t make it a sharedFonts, as there are multiple ubuntu applications in the store for different versions, which would conflict system-wide.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:23:07 +00:00
claunia commented 2026-01-31 05:23:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2022):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10359 for more discussion.

/dup #10359

@zadjii-msft commented on GitHub (Feb 17, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10359 for more discussion. /dup #10359
claunia commented 2026-01-31 05:23:08 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 17, 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 (Feb 17, 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:23:09 +00:00
Author
Owner
Copy Link

@didrocks commented on GitHub (Feb 17, 2022):

@zadjii-msft Thanks, sorry for not finding the duplicate first. Should I open another bug for the font part?

@didrocks commented on GitHub (Feb 17, 2022): @zadjii-msft Thanks, sorry for not finding the duplicate first. Should I open another bug for the font part?
claunia commented 2026-01-31 05:23:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2022):

Nah that's fine, I updated the title of that one to include the font part. Presumably, if we can fix it for icons, it should work the same for fonts.

@zadjii-msft commented on GitHub (Feb 17, 2022): Nah that's fine, I updated the title of that one to include the font part. Presumably, if we can fix it for icons, it should work the same for fonts.
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 Issue-Feature 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#16800
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?