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

Right-click on File Explorer on Windows system to launch, the new environment variable is invalid #13835

Closed
with-zeal opened this issue Aug 24, 2022 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@with-zeal
Copy link

Windows Terminal version

No response

Windows build number

No response

Other Software

Windows 11

Steps to reproduce

Create a new environment variable, right-click in file explorer on windows system to start Windows Terminal, try to execute the environment variable, but it is not valid.

Expected Behavior

No response

Actual Behavior

Right-click to start Windows Terminal in File Explorer on Windows systems, and the new environment variable is invalid, and the other way I know it works. After the computer restarts, file explorer right-clicks to start Windows Terminal.

@with-zeal with-zeal added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Aug 24, 2022
@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 Aug 24, 2022
@zadjii-msft
Copy link
Member

Was another Terminal already running when you tried to launch the terminal that ultimately didn't have the new environment variable? I'm betting we bounced through the old instance, which didn't have the env var, and lost the updated value.

I think this'll ultimately be fixed by #1125...

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 24, 2022
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 28, 2022
@ghost
Copy link

ghost commented Aug 28, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Aug 31, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

2 participants