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

Right-click on File Explorer on Windows system to launch, the new environment variable is invalid #18293

New Issue
Closed
opened 2026-01-31 06:09:34 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:09:34 +00:00
Owner
Copy Link

Originally created by @with-zeal on GitHub (Aug 24, 2022).

Windows Terminal version

No response

Windows build number

No response

Other Software

Windows 11

Steps to reproduce

Create a new environment variable, right-click in file explorer on windows system to start Windows Terminal, try to execute the environment variable, but it is not valid.

Expected Behavior

No response

Actual Behavior

Right-click to start Windows Terminal in File Explorer on Windows systems, and the new environment variable is invalid, and the other way I know it works. After the computer restarts, file explorer right-clicks to start Windows Terminal.

Originally created by @with-zeal on GitHub (Aug 24, 2022). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software Windows 11 ### Steps to reproduce Create a new environment variable, right-click in file explorer on windows system to start Windows Terminal, try to execute the environment variable, but it is not valid. ### Expected Behavior _No response_ ### Actual Behavior Right-click to start Windows Terminal in File Explorer on Windows systems, and the new environment variable is invalid, and the other way I know it works. After the computer restarts, file explorer right-clicks to start Windows Terminal.
claunia commented 2026-01-31 06:09:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2022):

Was another Terminal already running when you tried to launch the terminal that ultimately didn't have the new environment variable? I'm betting we bounced through the old instance, which didn't have the env var, and lost the updated value.

I think this'll ultimately be fixed by #1125...

@zadjii-msft commented on GitHub (Aug 24, 2022): Was another Terminal already running when you tried to launch the terminal that ultimately didn't have the new environment variable? I'm betting we bounced through the old instance, which didn't have the env var, and lost the updated value. I think this'll ultimately be fixed by #1125...
claunia commented 2026-01-31 06:09:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 28, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 28, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#18293
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?