Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Terminal does not sync environment variable changes #15041

Closed
Boilerplate4u opened this issue Mar 24, 2023 · 2 comments
Closed

Terminal does not sync environment variable changes #15041

Boilerplate4u opened this issue Mar 24, 2023 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Boilerplate4u
Copy link

Boilerplate4u commented Mar 24, 2023 •
edited
Loading

Windows Terminal version

1.17.1023

Windows build number

10.0.20348 Build 20348

Steps to reproduce

Terminal does not sync environment variable changes even if you close and open a new cmd/powershell session, ie you are forced close all sessions and restart Terminal before it takes effect.

Expected Behavior

It should sync environment variable changes at least when closing/opening a new sessions but even better live. You really shouldn't have to close all sessions and restart the whole Terminal for this.

Actual Behavior

It doesn't sync environment variable changes even if a cmd/powershell session is restarted (as a standalone cmd does)
@Boilerplate4u Boilerplate4u added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Mar 24, 2023
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1125 for more discussion.

/dup #1125

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Mar 24, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Boilerplate4u @zadjii-msft