pgcudahy
pgcudahy

Reputation: 1601

VScode remote not using the same path as vscode locally

I've been working on some Jupyter notebooks in VSCode. Jupyter isn't very git friendly, so when I want to commit my notebooks to Git, I have a filter that scrubs the output by using jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to=notebook --stdin --stdout.

This works fine locally with git commits in VSCode in the source control view (⌃⇧G).

However when I connect to the same machine remotely via VSCode, I get errors that jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to=notebook --stdin --stdout --log-level=ERROR: 1: jupyter: not found.
Jupyter is in my $PATH and works locally. It also works when I use the terminal window in a remote VSCode session. It only fails in the remote source control view. Any ideas?

Upvotes: 2

Views: 718

Answers (1)

VonC
VonC

Reputation: 1325137

It depends on where you defined your PATH: .profile or .bashrc.

Ctrl + Shift + P and then type Open Settings (JSON), and simply add the following line.

"terminal.integrated.inheritEnv": true

Upvotes: 1

Related Questions