How to prevent the vscode-quarto-extension using an old pre-installed version of Quarto?

[bgctw]

I want to use a recent version of Quarto on a shared server (accessed by vscode remote extension).
Therefore, I installed quarto using conda, queried its path, and specified this path via vscode quarto.path setting.

However, on this server there is an old installation of RStudio-server including Quarto 1.4. Although this server is not in the path, the vscode quarto extension is using RStudio-version, no matter of what I specify with the vscode quarto.path setting and if I kill and restart the remote vscode server.

The problem seems to be that the quarto.path setting only takes effect, if quarto is not in the PATH, but somehow, the old installation is added to the path by the vscode-quarto-extension.
A quick search for rstudio-server pointed to: quarto.ts.

How can I tell the quarto-extension to use a different executable than the old one?

[mcanouil]

I think that's a duplicate of:

• VS Code extension: quarto.path does not have any impact. #352

[bgctw]

The workaround in the cited issue worked for me:

After poking around in my settings and the terminal, I realized that my custom quarto.path is correctly added when I use bash shells, but not zsh or fish shells.

Quarto doesn't have a "default terminal profile" option, but setting "terminal.integrated.defaultProfile.osx": "bash" results in quarto preview using the expected Quarto binary. Changing the global terminal profile isn't optimal (I'd prefer not to use bash all the time), but it's nice to have a way around this problem.