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

Feature Request New shell tab should read path settings again #2710

Closed
dotnetshadow opened this issue Sep 10, 2019 · 2 comments
Closed

Feature Request New shell tab should read path settings again #2710

dotnetshadow opened this issue Sep 10, 2019 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

@dotnetshadow
Copy link

dotnetshadow commented Sep 10, 2019 •
edited
Loading

Description of the new feature/enhancement

I had the windows terminal open.
I was installing node at the same time.
After installation I tried node --version it couldn't find it, because the current window terminal session path didn't have node in it.

I added a new Powershell tab, and I found it too failed, when I entered node --version. I had to close Windows Terminal and open it again for it to work

Perhaps when you add a new tab, it should grab the latest path?
@dotnetshadow dotnetshadow added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 10, 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 Sep 10, 2019
@dotnetshadow dotnetshadow changed the title Feature Request - New shell should read path settings again Feature Request - New shell tab should read path settings again Sep 10, 2019
@dotnetshadow dotnetshadow changed the title Feature Request - New shell tab should read path settings again Feature Request New shell tab should read path settings again Sep 10, 2019
@zadjii-msft
Copy link
Member

I'm pretty sure this is actually a dupe of #1125

I'm not positive, so someone yank the duplicate tag if I'm wrong

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Sep 11, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Sep 11, 2019
@dotnetshadow
Copy link
Author

Cheers yes looks like duplicate, didn't see it when I searched, thanks

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. 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
@dotnetshadow @zadjii-msft