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.

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

Reload PATH when opening new Powershell instance #3605

Closed
KSiig opened this issue Nov 16, 2019 · 3 comments
Closed

Reload PATH when opening new Powershell instance #3605

KSiig opened this issue Nov 16, 2019 · 3 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

@KSiig
Copy link

KSiig commented Nov 16, 2019

Description of the new feature/enhancement

When opening a new Powershell tab, it seems to use the same PATH that was present when opening Terminal. It would be nice if it used the updated path, like what you'd expect from opening a new tab in Linux.

I just installed node, and was wondering why the node -v command wouldn't work. Opened a regular powershell instance and it worked, which is why I believe it simply stems from Terminal not reloading the PATH.

@KSiig KSiig added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 16, 2019
@ghost ghost 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 Nov 16, 2019
@piotrpalek
Copy link

I just wanted to open the same issue :)

In addition to the above, opening splits should also keep the current PATH / working directory.

@zadjii-msft
Copy link
Member

Thanks for the report! This is actually something that's already being tracked in another thread. I'll redirect discussion there:

/dup #1125

@ghost
Copy link

ghost commented Nov 18, 2019

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 ghost closed this as completed Nov 18, 2019
@ghost ghost 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 Nov 18, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants