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

New tabs should re-read environment variable list. #14948

Closed
GarThor opened this issue Mar 3, 2023 · 4 comments
Closed

New tabs should re-read environment variable list. #14948

GarThor opened this issue Mar 3, 2023 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@GarThor
Copy link

GarThor commented Mar 3, 2023

Description of the new feature/enhancement

I'm not really sure if this should be filed as an issue or not, but I'm changing projects, and thusly environment variables all the time. Unfortunately, the terminal app runs as a single app, and never re-reads environment variables from the windows environment, which means I have to remember to close and re-open terminal if I want to see those changes. It would be nice if there was a button that would let me explicitly refresh the environment for a specific tab... at the very least closing and re-opening a tab should re-read the environment variables into the new shell for use.

Proposed technical implementation details (optional)

When I open a new terminal tab, it should have the most up-to-date version of all environment variables and other settings that I've set. This should be done in a predictable way, such that any process running in other tabs should retain the previous version of the environment variables, so that any processes running in those tabs doesn't get confused.
@GarThor GarThor added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 3, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added 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 3, 2023
@DHowett
Copy link
Member

DHowett commented Mar 3, 2023

Thanks for the report! This is the topic of pull request #14839, which is associated with bug #1125. I've got good news: it looks like it's trending towards merging!

I'd suggest following /dup #1125 for a little longer, and jumping on the Preview channel when 1.18 is released. 😄

@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. 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 3, 2023
@GarThor
Copy link
Author

GarThor commented Mar 3, 2023

Thanks so much @DHowett , I did search for the issue, and didn't immediately find anything that resembled this issue, but I suppose I just needed to dig a little deeper. I'll go ahead and take a look at the issues you posted, and then wait eagerly for the latest version! =D

@DHowett
Copy link
Member

DHowett commented Mar 3, 2023

Oh, yeah, they're totally cryptic. We have a (bad?) habit of naming issues after the engineering work needed to do them rather than the observable bug. Sometimes. 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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
@DHowett @GarThor