Preview no longer available in VSCode

[mcanouil]

I no longer have the prompt (or the preview panel) that ask where to preview the generated HTML file either Windows 10 / MacOS 12.4, while I stil have it within a Docker container running Debian.
The settings were not modified (i.e., default). Any idea, how to fix this, if not on quarto-vscode side?

Also, I think path resolution for the preview has a bug when trying to render/preview subfolder/file.qmd and setting _quarto.yml with execute-dir: project.
This results in VSCode prompting the user to choose external browser or editor, but in both cases this ends with:

...

Output created: index.html

Watching files for changes
Browse at http:///localhost:6840/subfolder/index.html
GET: / (404: Not Found)

OS: Windows 10 / MacOS 12.4
VSCode: 1.68
quarto-vscode: 1.24
Quarto: 0.9.573

[jjallaire]

I don't seem to be able to reproduce this problem w/ the latest quarto/vscode extension on osx. Could you provide a link to a git repo that exhibits this behavior as well as the specific action you took in VS Code (something in the terminal, keyboard shortcut, etc.) to get into this state.

[mcanouil]

I am testing different setup to make a reproducible and working example and get back here with more details.

[mcanouil]

I tried on an independent instance of VSCode (without my settings/extensions) using a controlled and identical setup.
With my settings and extension, the issue appears, it does not on the independent instance of VSCode.

This issue is now likely to be a conflict with one of my ~ 40 extensions ^^

[mcanouil]

I found the issue/conflict.
Because Quarto extension works in the terminal it is subordinate to it, i.e., Quarto does not support "terminal.integrated.shellIntegration.enabled": true.
Example in https://github.com/mcanouil/quarto-issues/tree/main/quarto-cli-1154

EDIT: both issues raised in the first message are in fact the same issue coming from shell integration, i.e., disabling it solves both.

[jjallaire]

Thank you! That's great slue-thing. Unfortunately it looks like this is a VS Code bug. When this setting is active its impossible for us to forward environment variable to quarto preview (which we do here: https://github.com/quarto-dev/quarto-vscode/blob/df686596c2bc9fecc6bb4894e2f1d3a44fb0c93f/src/providers/preview/preview-env.ts#L12-L13).

[mcanouil]

I thought it was something related to the "interception" caused by shell integration.
Now that I know what's the issue, I can disable shell integration locally in the workspace, as per the reproducible example.
Thanks!

[jjallaire]

Thanks again for your help sorting this out. I think that this is an important enough (and sufficiently hard to discover) workaround that it should be applied automatically if you are working on Quarto documents within a workspace. I did this here: quarto-dev/quarto-vscode@0494725