Skip to content

docs: warning about environment variables#4761

Merged
benfdking merged 3 commits intomainfrom
docs_warning_about_env_vars
Jun 19, 2025
Merged

docs: warning about environment variables#4761
benfdking merged 3 commits intomainfrom
docs_warning_about_env_vars

Conversation

@benfdking
Copy link
Copy Markdown
Contributor

No description provided.

Comment thread docs/guides/vscode.md Outdated
Comment thread docs/guides/vscode.md Outdated

The extension runs the language server in a separate process. This inherits the environment variables of the parent vscode instance but it does not necessarily inherit the environment variables of the terminal instance. This means that if you have environment variables set in your VSCode terminal, they will not necessarily be available to the language server. Making sure that the language server has access to any variables you call upon can either be done by ensuring the variables are set in the environment the LSP runs:

- by opening vscode from a terminal that has the variables set
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- by opening vscode from a terminal that has the variables set
- Open VSCode from a terminal instance that has the variables set
- By default, the command `code` opens VSCode from a terminal instance

Comment thread docs/guides/vscode.md Outdated
Comment thread docs/guides/vscode.md Outdated
@benfdking benfdking force-pushed the docs_warning_about_env_vars branch from b2733d3 to 25d4b08 Compare June 19, 2025 11:24
@benfdking benfdking enabled auto-merge (squash) June 19, 2025 11:25
@benfdking benfdking merged commit c88daec into main Jun 19, 2025
24 checks passed
@benfdking benfdking deleted the docs_warning_about_env_vars branch June 19, 2025 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants