New Tabs do not read Environmental variables a-new #11330

Closed
opened 2026-01-31 02:44:42 +00:00 by claunia · 3 comments
Owner

Originally created by @kingfetty on GitHub (Nov 10, 2020).

WindowTerminal Version: 1.3.2651.0
Windows 10 1909 build 18363.1139

Summary:

If you've already opened windows terminal and change an environmental variable such as PATH and then spawn a new tab, the new tab does not include the latest updates to the variable. This requires users to completely close the entire windows terminal application to get it to read the variable. Each sub process / tab should read the environment variables anew on spawn preventing the need to close any windows that may be open already and losing possible work in the process.

To reproduce:

  • Open Windows Terminal and have an existing window opened
  • Change the system path to include a new test item in the path
  • spawn a new tab in the existing windows terminal
  • echo the system path and note that the changed path is not included
Originally created by @kingfetty on GitHub (Nov 10, 2020). WindowTerminal Version: 1.3.2651.0 Windows 10 1909 build 18363.1139 **Summary:** If you've already opened windows terminal and change an environmental variable such as PATH and then spawn a new tab, the new tab does not include the latest updates to the variable. This requires users to completely close the entire windows terminal application to get it to read the variable. Each sub process / tab should read the environment variables anew on spawn preventing the need to close any windows that may be open already and losing possible work in the process. **To reproduce:** - Open Windows Terminal and have an existing window opened - Change the system path to include a new test item in the path - spawn a new tab in the existing windows terminal - echo the system path and note that the changed path is not included
claunia added the Resolution-Duplicate label 2026-01-31 02:44:42 +00:00
Author
Owner

@j4james commented on GitHub (Nov 10, 2020):

I think this might be a dup of #1125.

@j4james commented on GitHub (Nov 10, 2020): I think this might be a dup of #1125.
Author
Owner

@DHowett commented on GitHub (Nov 10, 2020):

Indeed. This was fixed in #7243, but I have been holding it back from Stable builds because it breaks WOW64 PowerShell. (#7418). /dup #7243

@DHowett commented on GitHub (Nov 10, 2020): Indeed. This was fixed in #7243, but I have been holding it back from Stable builds because it breaks WOW64 PowerShell. (#7418). /dup #7243
Author
Owner

@ghost commented on GitHub (Nov 10, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 10, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11330