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

Set environment variable WT_FOLDER_PATH to the folder path that contains WindowsTerminal.exe #20794

New Issue
Closed
opened 2026-01-31 07:24:16 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 07:24:16 +00:00
Owner
Copy Link

Originally created by @daxgames on GitHub (Nov 12, 2023).

Originally assigned to: @zadjii-msft on GitHub.

Description of the new feature/enhancement

Set an environment variable WT_FOLDER_PATH to the folder path that contains WindowsTerminal.exe. This variable should be set when Windows Terminal launches before the profile is launched.

This would be useful for users that run Windows Terminal in portable mode so Windows terminal profiles can be configured with paths relative to the folder wher WIndows Terminal is installed as shown below:

image

The normal user profile is configured as shown below and works perfectly because the %CMDER_ROOT% env variable was set dynamically before launching Windows Terminal.

image

The above configuration does not work when launching as Administrator because the %CMDER_ROOT% env variable is not set globally on the system nor in the Administator's personal environment variables. it produces the error below:

image

For completeness sake the icon config being complained about in the error above is below:

image

Proposed technical implementation details (optional)

Originally created by @daxgames on GitHub (Nov 12, 2023). Originally assigned to: @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> Set an environment variable `WT_FOLDER_PATH` to the folder path that contains `WindowsTerminal.exe`. This variable should be set when Windows Terminal launches before the profile is launched. This would be useful for users that run Windows Terminal in portable mode so Windows terminal profiles can be configured with paths relative to the folder wher WIndows Terminal is installed as shown below: ![image](https://github.com/microsoft/terminal/assets/7318053/f77f8e2c-7c8e-48d1-a4ce-81038c653468) The normal user profile is configured as shown below and works perfectly because the `%CMDER_ROOT%` env variable was set dynamically before launching Windows Terminal. ![image](https://github.com/microsoft/terminal/assets/7318053/1bc3f646-e05d-4e69-8add-b8422a8cea90) The above configuration does not work when launching as Administrator because the `%CMDER_ROOT%` env variable is not set globally on the system nor in the Administator's personal environment variables. it produces the error below: ![image](https://github.com/microsoft/terminal/assets/7318053/ffd23d64-329c-4ae1-8e66-ebe36b563d4f) For completeness sake the icon config being complained about in the error above is below: ![image](https://github.com/microsoft/terminal/assets/7318053/7b878169-edfc-4046-9ea6-453c91703b4a) # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 07:24:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 13, 2023):

This really falls under the same problem space as #13006 et al. We could add that, sure,

Wait, no it doesn't. This is actually so simple. Set that variable for terminal itself. So that we can resolve things relative to ourself. brilliant.

I think we were already tracking this in #15379 but I'll motion to use this as the tracking thread instead, since this has a real good idea. Thanks!

@zadjii-msft commented on GitHub (Nov 13, 2023): ~This really falls under the same problem space as #13006 et al. We could add that, sure,~ Wait, no it doesn't. This is actually so simple. Set that variable _for terminal itself_. So that we can resolve things relative to ourself. brilliant. I think we were already tracking this in #15379 but I'll motion to use this as the tracking thread instead, since this has a real good idea. Thanks!
claunia commented 2026-01-31 07:24:18 +00:00
Author
Owner
Copy Link

@daxgames commented on GitHub (May 28, 2024):

The implemented solution in https://github.com/microsoft/terminal/pull/16949:

  1. Is confusing.
  • Is it %WT_SETTINGS_DIR% or %WT_SETTINGS_PATH%
  • I THINK it is %WT_SETTINGS_DIR% because it seems to MOSTLY work.
  • Does not COMPLETELY solve this issue. See below.

New Config:

image

Launching the profile:

image

The paths exist because the shell is configured using "%WT_SETTINGS_DIR%\..\..\init.bat" and the tab icon is correctly read from "%WT_SETTINGS_DIR%......\icons\cmder_red.ico".

@daxgames commented on GitHub (May 28, 2024): The implemented solution in https://github.com/microsoft/terminal/pull/16949: 1. Is confusing. - Is it `%WT_SETTINGS_DIR%` or `%WT_SETTINGS_PATH%` - I THINK it is `%WT_SETTINGS_DIR%` because it seems to MOSTLY work. - Does not COMPLETELY solve this issue. See below. New Config: ![image](https://github.com/microsoft/terminal/assets/7318053/babb8c42-ecfd-41aa-ac1d-3399ed792e65) Launching the profile: ![image](https://github.com/microsoft/terminal/assets/7318053/d7cdf647-5dcb-4373-9f47-820123d9f38d) The paths exist because the shell is configured using `"%WT_SETTINGS_DIR%\..\..\init.bat"` and the tab icon is correctly read from "%WT_SETTINGS_DIR%\..\..\..\icons\cmder_red.ico".
claunia commented 2026-01-31 07:24:18 +00:00
Author
Owner
Copy Link

@daxgames commented on GitHub (May 28, 2024):

Also why can't this just be a normal env variable like the below that are set in 1.20.x:

image

Like this:

image

@daxgames commented on GitHub (May 28, 2024): Also why can't this just be a normal env variable like the below that are set in 1.20.x: ![image](https://github.com/microsoft/terminal/assets/7318053/b0919fc3-35ef-46df-bdd3-ef2058ba9854) Like this: ![image](https://github.com/microsoft/terminal/assets/7318053/d1fd464c-7f2d-4dc0-89c3-679b89d01aef)
claunia commented 2026-01-31 07:24:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2024):

Image

It's WT_SETTINGS_DIR 😄
(It may not work in the commandline field - we need to investigate that. It should work in any other field in the settings that supports paths.)

@DHowett commented on GitHub (May 28, 2024): ![Image](https://github.com/microsoft/terminal/assets/189190/b95a9df2-e551-47c9-b778-5c1f2ab6e7e5) It's `WT_SETTINGS_DIR` 😄 (It may not work in the commandline field - we need to investigate that. It should work in any other field in the settings that supports paths.)
claunia commented 2026-01-31 07:24:18 +00:00
Author
Owner
Copy Link

@daxgames commented on GitHub (May 28, 2024):

See my edited comment above.

@daxgames commented on GitHub (May 28, 2024): See my edited comment above.
claunia commented 2026-01-31 07:24:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2024):

Thanks!

@DHowett commented on GitHub (May 28, 2024): Thanks!
claunia commented 2026-01-31 07:24:19 +00:00
Author
Owner
Copy Link

@daxgames commented on GitHub (May 28, 2024):

Thanks for the quick response and the fix!

I looked at the PR and it went back and forth on %WT_SETTINGS_DIR% and %WT_SETTINGS_PATH%. After posting the issue I went to the Release Notes and saw the correct env var but it still throws the icon message. Other than that it all works!

My only other concern is wrapping the icon path with double quotes causes it to fail. Not sure if that would be an issue if the icon were in a path that contained spaces.

@daxgames commented on GitHub (May 28, 2024): Thanks for the quick response and the fix! I looked at the PR and it went back and forth on `%WT_SETTINGS_DIR%` and `%WT_SETTINGS_PATH%`. After posting the issue I went to the Release Notes and saw the correct env var but it still throws the icon message. Other than that it all works! My only other concern is wrapping the icon path with double quotes causes it to fail. Not sure if that would be an issue if the icon were in a path that contained spaces.
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 Area-Settings Help Wanted In-PR Issue-Task Needs-Tag-Fix Product-Terminal
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#20794
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?