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

How to know the value of Dynamic profiles path? #15057

New Issue
Closed
opened 2026-01-31 04:27:12 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:27:12 +00:00
Owner
Copy Link

Originally created by @stephane-archer on GitHub (Sep 1, 2021).

I would like to know the path in my current config for Windows.Terminal.Wsl
Where is it pointing to?

Originally created by @stephane-archer on GitHub (Sep 1, 2021). I would like to know the path in my current config for Windows.Terminal.Wsl Where is it pointing to?
claunia commented 2026-01-31 04:27:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 1, 2021):

It's pointing at a profile that's created at runtime for your WSL distros. It doesn't really exist anywhere. There are more docs on dynamic profiles here. Could you maybe share more details on what you're trying to do? I'm not really sure how best to answer your question.

@zadjii-msft commented on GitHub (Sep 1, 2021): It's pointing at a profile that's created at runtime for your WSL distros. It doesn't really exist _anywhere_. There are more docs on dynamic profiles [here](https://docs.microsoft.com/en-us/windows/terminal/dynamic-profiles). Could you maybe share more details on what you're trying to do? I'm not really sure how best to answer your question.
claunia commented 2026-01-31 04:27:14 +00:00
Author
Owner
Copy Link

@stephane-archer commented on GitHub (Sep 1, 2021):

All the other profiles have a path to the shell they run or the name of the exe they run, for example: "commandline": "powershell.exe",
I would like to know basically what is run by the profile Windows.Terminal.Wsl on my particular laptop.
From my understanding, because it's using WSL, it's not calling bash.exe somewhere in my system

@stephane-archer commented on GitHub (Sep 1, 2021): All the other profiles have a path to the shell they run or the name of the exe they run, for example: `"commandline": "powershell.exe",` I would like to know basically what is run by the profile `Windows.Terminal.Wsl` on my particular laptop. From my understanding, because it's using WSL, it's not calling `bash.exe` somewhere in my system
claunia commented 2026-01-31 04:27:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 1, 2021):

Ah okay. They're basically all just doing wsl -d {the name of the distro}. They're generated here:

c089ae0c57/src/cascadia/TerminalSettingsModel/WslDistroGenerator.cpp (L168)

@zadjii-msft commented on GitHub (Sep 1, 2021): Ah okay. They're basically all just doing `wsl -d {the name of the distro}`. They're generated here: https://github.com/microsoft/terminal/blob/c089ae0c57d9ecc6d6e0f99eeb6cbcb655bd720e/src/cascadia/TerminalSettingsModel/WslDistroGenerator.cpp#L168
claunia commented 2026-01-31 04:27:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 1, 2021):

You can also learn this by looking into the profile in the Settings UI! 😄

image

@DHowett commented on GitHub (Sep 1, 2021): You can also learn this by looking into the profile in the Settings UI! :smile: ![image](https://user-images.githubusercontent.com/189190/131736193-1d92153a-37f1-4466-88c6-e8c7ecd573ea.png)
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-Docs Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
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#15057
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?