Initial failure to detect jupytext when remote editing

[td-anne]

When I start a new remote project window, I always get a popup telling me that this extension cannot find a jupytext executable. This occurs even for projects where I have explicitly set the path to the python executable to run jupytext with (in workspace settings). The extension appears to work fine, updating the .py files when I edit my .ipynb files remotely.

I suspect this might be an issue related to #9, where the extension is attempting to run on the local machine as well as the remote one. The local copy cannot of course find the python executable at the specified path, since this does not exist on the local machine. As the project files also do not exist on the local machine, running a local jupytext could not work anyway.

[caenrigen]

Thanks for reporting this one too, Anne.

Unfortunately I never used the remote project feature of VS Code. I did not yet need such set up.

I am glad that it actually works despite the warning.

I don't have bandwidth to look into this. PRs are welcome though