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] Support optional property TerminalOptions#strictEnv #11143

Closed
Tracked by #9863
planger opened this issue May 12, 2022 · 1 comment · Fixed by #11641
Closed
Tracked by #9863

[vscode] Support optional property TerminalOptions#strictEnv #11143

planger opened this issue May 12, 2022 · 1 comment · Fixed by #11641
Assignees
Labels
terminal issues related to the terminal vscode issues related to VSCode compatibility

Comments

@planger
Copy link
Contributor

planger commented May 12, 2022

Feature Description:

Add support for TerminalOptions#strictEnv to allow specifying whether the terminal should be exactly as provided in TerminalOptions.env, see https://code.visualstudio.com/api/references/vscode-api#TerminalOptions.

@vince-fugnitto vince-fugnitto added terminal issues related to the terminal vscode issues related to VSCode compatibility labels May 12, 2022
@planger
Copy link
Contributor Author

planger commented Sep 2, 2022

I'll look into this issue.

planger added a commit to eclipsesource/theia that referenced this issue Sep 7, 2022
Fixes eclipse-theia#11143
Contributed on behalf of STMicroelectronics.

Change-Id: Iabeb2c9a9dac27891e43a011db86b5e37e8a3120
martin-fleck-at pushed a commit that referenced this issue Sep 15, 2022
Fixes #11143
Contributed on behalf of STMicroelectronics.

Change-Id: Iabeb2c9a9dac27891e43a011db86b5e37e8a3120
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
terminal issues related to the terminal vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants