On Windows, environment variable values are not refreshed without restart
Open
Nobody has claimed this yet.
1 vote
enhancement
windows
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Windows Explorer listens for the WM_SETTINGCHANGE message which is broadcast when environment variables are changed. fman would ideally do the same
A consequence of this is that other executables launched from fman can launch with an out-of-date environment.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the fman entry point that launches child executables and researching how Windows broadcasts WM_SETTINGCHANGE when environment variables change. The issue names no file or test; done means newly launched executables receive refreshed environment values without restarting fman.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100