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

BUG: Launched programs have old environment variables #2694

Open
2 tasks done
nref opened this issue May 10, 2024 · 3 comments
Open
2 tasks done

BUG: Launched programs have old environment variables #2694

nref opened this issue May 10, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@nref
Copy link

nref commented May 10, 2024

Checks

  • I have checked that this issue has not already been reported.

  • I am using the latest version of Flow Launcher.

Problem Description

Programs launched with Flow have the environment variables that were set when Flow started.

To Reproduce

I was debugging in Visual Studio 2022. My program loads a configuration value from an envrionment variable. When I change the variable and re-launch VS with Flow, the new instance of VS has the old env vars. If I re-launch VS from the Start Menu, it has the new env vars.

Screenshots

No response

Flow Launcher Version

1.18.0

Windows Build Number

Microsoft Windows [Version 10.0.22631.3527]

Error Log

No response

@nref nref added the bug Something isn't working label May 10, 2024
@nref
Copy link
Author

nref commented May 10, 2024

Thanks for a nice launcher.

@deefrawley
Copy link
Member

Not a fix, but you can hit F5 to refresh Flow when you know an environment variable has changed.

@nref
Copy link
Author

nref commented May 15, 2024

Thanks mate. I didn't know about that. I'm totally willing to hit F5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants