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

VSCode Insiders: Integrated terminal has a LANG=en_US.UTF-8 env variable declared #35550

Closed
Nazeehe opened this issue Oct 3, 2017 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug linux Issues with VS Code on Linux terminal Integrated terminal issues windows VS Code on Windows issues
Milestone

Comments

@Nazeehe
Copy link

Nazeehe commented Oct 3, 2017

  • VSCode Version: Insiders 1.17.0
  • OS Version: Windows 10

Steps to Reproduce:

  1. Set up a Windows CMD integrated terminal window
  2. Launch it and inspect environment variables
  3. Notice the LANG env variable? Where did that come from?

This env variable is messing with my build at work (Microsoft, Razzle).

Reproduces without extensions: Yes

More info: Found the issue in the code:
d:\vscode-master\src\vs\workbench\parts\terminal\electron-browser\terminalInstance.ts
public static createTerminalEnv
env['LANG'] = TerminalInstance._getLangEnvVariable(locale);

More info:
This is the issue that introduced this as a fix: #14586

Is there a way to not make it set those?

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Oct 3, 2017
@Tyriar
Copy link
Member

Tyriar commented Oct 3, 2017

Is the variable causing particular issues? This is an environment variable used on Linux/macOS but should also be useful for WSL bash sessions.

@Tyriar Tyriar added the info-needed Issue requires more information from poster label Oct 3, 2017
@Nazeehe
Copy link
Author

Nazeehe commented Oct 3, 2017

Hey Tyriar,

Yeah, I got a build error building Windows due to this env variable being set. I am using VSCode with my Razzle window at Microsoft. Once I unset it, the build succeeded.

It's an interesting thing though. I can see that you guys are setting a bunch of env variables in there for the terminal. You also provide a way for the user to add more. But no way to unset them?

Any how, I worked around it by having my startup script in razzle unset it. I am sure you guys will find a great way to fix it :)

@Tyriar
Copy link
Member

Tyriar commented Oct 4, 2017

Great to hear you got a workaround, I created #35586 to allow unsetting of environment vars via settings.

@Tyriar Tyriar closed this as completed Oct 4, 2017
@Tyriar Tyriar added *duplicate Issue identified as a duplicate of another issue(s) bug Issue identified by VS Code Team member as probable bug linux Issues with VS Code on Linux windows VS Code on Windows issues and removed *duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster labels Oct 4, 2017
@Tyriar Tyriar added this to the October 2017 milestone Oct 10, 2017
@Tyriar Tyriar reopened this Oct 10, 2017
@Tyriar Tyriar closed this as completed in a91bad4 Oct 10, 2017
@Tyriar Tyriar reopened this Oct 11, 2017
@Tyriar Tyriar modified the milestones: October 2017, Backlog Oct 30, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 28, 2017

I think this issue can be closed with the workaround of setting terminal.integrated.setLocaleVariables to false.

@Tyriar Tyriar closed this as completed Dec 28, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug linux Issues with VS Code on Linux terminal Integrated terminal issues windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

2 participants