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

Environment not inherited by new instances/tabs of windows terminal #12980

New Issue
Open
opened 2026-01-31 03:30:33 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 03:30:33 +00:00
Owner
Copy Link

Originally created by @HudsonMC16 on GitHub (Mar 11, 2021).

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0

Windows Terminal Preview
Version: 1.7.572.0

Steps to reproduce

Not sure this is exactly the right way to describe this issue and I'm not exactly sure how to test it explicitly, so I will describe the a short, (hopefully) reproducible situation in which I encountered this inconsistency between 1.6 and 1.7-preview.

  1. activate a python virtual environment
  2. run wt -d .
  3. in newly-opened terminal instance, run python
  4. at python repl, run import sys then sys.executable

Expected behavior

In 1.6 (non-preview), the new terminal instance would inherit the python environment from the calling terminal, so the above steps would print the path to the python interpreter inside the venv.

I used this behavior often in batch scripts to launch applications (mostly vim). The batch script (usually launched from the address bar in an explorer window) would check for a venv, if it existed, it would activate it then launch the application from inside the venv.

Actual behavior

In 1.7 (preview), the new terminal instance did not inherit the python environment and the above steps printed the path to the system python interpreter.

Originally created by @HudsonMC16 on GitHub (Mar 11, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0 ``` ``` Windows Terminal Preview Version: 1.7.572.0 ``` # Steps to reproduce Not sure this is *exactly* the right way to describe this issue and I'm not exactly sure how to test it explicitly, so I will describe the a short, (hopefully) reproducible situation in which I encountered this inconsistency between 1.6 and 1.7-preview. 1) activate a python virtual environment 2) run `wt -d .` 3) in newly-opened terminal instance, run `python` 4) at python repl, run `import sys` then `sys.executable` # Expected behavior In 1.6 (non-preview), the new terminal instance would inherit the python environment from the calling terminal, so the above steps would print the path to the python interpreter inside the venv. I used this behavior often in batch scripts to launch applications (mostly vim). The batch script (usually launched from the address bar in an explorer window) would check for a venv, if it existed, it would activate it then launch the application from inside the venv. # Actual behavior In 1.7 (preview), the new terminal instance did not inherit the python environment and the above steps printed the path to the system python interpreter.
claunia added the Resolution-Duplicate label 2026-01-31 03:30:33 +00:00
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 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#12980
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?