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

how to disable WT_SETTINGS_DIR for nonportable Windows Terminal? #22310

New Issue
Closed
opened 2026-01-31 08:09:29 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:09:29 +00:00
Owner
Copy Link

Originally created by @candrapersada on GitHub (Sep 24, 2024).

How to disable WT_SETTINGS_DIR for Windows Terminal installed from the Microsoft Store?
and enable WT_SETTINGS_DIR from Environment Variables

Originally created by @candrapersada on GitHub (Sep 24, 2024). How to disable `WT_SETTINGS_DIR` for `Windows Terminal` installed from the Microsoft Store? and enable `WT_SETTINGS_DIR` from `Environment Variables`
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 08:09:29 +00:00
claunia commented 2026-01-31 08:09:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 24, 2024):

Can you explain your use case a bit more? WT_SETTINGS_DIR is expected to point to the actual settings directory Terminal was started with; it cannot use and does not use the one you set. Did you add one to your environment block so that you could use it to refer to WT settings you stored somewhere other than the settings directory?

@DHowett commented on GitHub (Sep 24, 2024): Can you explain your use case a bit more? `WT_SETTINGS_DIR` is expected to point to the actual settings directory Terminal was started with; it cannot use and does not use the one you set. Did you add one to your environment block so that you could use it to refer to WT settings you stored somewhere _other than_ the settings directory?
claunia commented 2026-01-31 08:09:30 +00:00
Author
Owner
Copy Link

@candrapersada commented on GitHub (Sep 24, 2024):

Did you add one to your environment block so that you could use it to refer to WT settings you stored somewhere other than the settings directory?

yes to change the settings location with use Environment Variables

@candrapersada commented on GitHub (Sep 24, 2024): > Did you add one to your environment block so that you could use it to refer to WT settings you stored somewhere _other than_ the settings directory? yes to change the settings location with use `Environment Variables`
claunia commented 2026-01-31 08:09:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 24, 2024):

Terminal does not read the location of its settings file from that variable. It never has. :)

@DHowett commented on GitHub (Sep 24, 2024): Terminal does not read the location of its settings file from that variable. It never has. :)
claunia commented 2026-01-31 08:09:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 24, 2024):

We are not planning on supporting a configurable settings location using an environment variable right now. Sorry!

@DHowett commented on GitHub (Sep 24, 2024): We are not planning on supporting a configurable settings location using an environment variable right now. Sorry!
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 Needs-Tag-Fix Needs-Triage
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#22310
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?