microsoft / microsoft/PowerToys
I have a question but there's no template for a question
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
### Microsoft PowerToys version
0.1
### Installation method
PowerToys auto-update
### Area(s) with issue?
Environment Variables
### Steps to reproduce
General Question about environmental variable creation and elimination.
I was looking for a variable that was created under a process I was debugging. I can't seem to find it anywhere. Shouldn't I be able to see it if it's referenced in a script that referenced it even if it's null? Or is it literally not a variable if null?
1. If the variable processFound first appears as shown below would it be created as an environmental variable at this point?
Set "processFound="
2. If the answer is to #1 is NO would it appear in the Environment Variables after the statement below?
Set "processFound=1"
If the answer to #1 was YES than the question above is irrelevant as the value would be updated.
If the answer to #2 was YES then would it be removed from the Environment Variables if I executed the statement below?
Set "processFound="
If the answer to #2 was NO then I have a problem.
If the answer to #3 is YES than I'm good.
If the answer to #3 is NO then how and when is it removed from the Environmental Variables?
Would it show under my profile or the system? What determines which list it become part of?
### ✔️ Expected Behavior
_No response_
### ❌ Actual Behavior
_No response_
### Upload Bug Report ZIP-file
_No response_
### Additional Information
_No response_
### Other Software
_No response_
Contributor guide
Research direction
No file, test, or entry point is identified. First clarify whether this is a support question or a documentation change, then verify the described cmd.exe SET behavior and the distinction between process, user, and system environment variables. Done would be a documented, authoritative answer or a narrowed documentation issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100