-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Some system-defined environment variables are undefined #7399
Labels
Area-TerminalConnection
Issues pertaining to the terminal<->backend connection interface
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Priority-1
A description (P1)
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Severity-Blocking
We won't ship a release like this! No-siree.
Milestone
Comments
Regressed w/ #7243. |
Should this block 1.3? |
Yeah probably. |
Investigating: profile API does EXPLICITLY add these vars (!) so i bet it's my token code |
nathpete-msft
added a commit
to nathpete-msft/terminal
that referenced
this issue
Aug 25, 2020
ghost
pushed a commit
that referenced
this issue
Aug 25, 2020
This fixes a regression in environment variable loading introduced as part of the new environment block creation that prevents some system-defined, volatile environment variables from being defined. ## References #7243 (comment) ## Validation Steps Performed Manually verified locally. Closes #7399
DHowett
pushed a commit
that referenced
this issue
Aug 25, 2020
This fixes a regression in environment variable loading introduced as part of the new environment block creation that prevents some system-defined, volatile environment variables from being defined. ## References #7243 (comment) ## Validation Steps Performed Manually verified locally. Closes #7399 (cherry picked from commit 64f10a0)
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-TerminalConnection
Issues pertaining to the terminal<->backend connection interface
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Priority-1
A description (P1)
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Severity-Blocking
We won't ship a release like this! No-siree.
Environment
Steps to reproduce
In Powershell:
$Env:UserName
In cmd:
echo %UserName%
It looks like this variable is defined here:
HKEY_CURRENT_USER\Volatile Environment
There are a couple of other variables defined there that are also undefined:
%USERDOMAIN%
and%USERDNSDOMAIN%
This is only happing after updating to the preview version of Terminal 1.3. The variables are still defined in Terminal 1.2, and when running pwsh/Windows Powershell/cmd outside of Terminal.
Expected behavior
The variable should contain the current user name.
Actual behavior
The variable is undefined.
The text was updated successfully, but these errors were encountered: