splitpane does not inherit parent environment variables. #7775

Open
opened 2026-01-31 01:12:18 +00:00 by claunia · 0 comments
Owner

Originally created by @kgfly on GitHub (Apr 28, 2020).

Environment

Windows build number: 10.0.18363.778
Windows Terminal version (if applicable): latest 

Any other software? VS.

Steps to reproduce

Add these setting to settings.json
{ "command": { "action": "splitPane", "split": "horizontal"}, "keys": "alt+," },
{ "command": { "action": "splitPane", "split": "vertical"}, "keys": "alt+." },

Press "alt+." to split

Expected behavior

The split pane should inherit parent environment variables.

Actual behavior

splitpane does not inherit parent environment variables.

Notes:

I think this is a bug because "alt-shift-d" split can inherit parent environment variables.

So
{ "command": { "action": "splitPane", "split": "horizontal"}, "keys": "alt+," },
{ "command": { "action": "splitPane", "split": "vertical"}, "keys": "alt+." },

should inherit parent environment variables too.

Originally created by @kgfly on GitHub (Apr 28, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Windows build number: 10.0.18363.778 Windows Terminal version (if applicable): latest Any other software? VS. ``` # Steps to reproduce Add these setting to settings.json { "command": { "action": "splitPane", "split": "horizontal"}, "keys": "alt+," }, { "command": { "action": "splitPane", "split": "vertical"}, "keys": "alt+." }, <!-- A description of how to trigger this bug. --> Press "alt+." to split # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The split pane should inherit parent environment variables. # Actual behavior <!-- What's actually happening? --> splitpane does not inherit parent environment variables. Notes: I think this is a bug because "alt-shift-d" split can inherit parent environment variables. So { "command": { "action": "splitPane", "split": "horizontal"}, "keys": "alt+," }, { "command": { "action": "splitPane", "split": "vertical"}, "keys": "alt+." }, should inherit parent environment variables too.
claunia added the Resolution-Duplicate label 2026-01-31 01:12:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7775