Repository navigation
Description
Bug description
After installing Quarto 1.6.39 the preview in VS Code no longer works,
for files with spaces in their name in a website project,
at least on first render.
Steps to reproduce
- put these files in a directory:
_quarto.yml:
project:
type: website
file with spaces.md:
this is `file with spaces.md`
other file with spaces.md:
this is `other file with spaces.md`
- open the directory with VS Code as a project
- open one of the md-files
- run the command "Quarto: Preview"
Expected behavior
The file should be processed and the resulting html file displayed in the "Quarto Preview" tab.
Actual behavior
The file is processed but not displayed
…
Output created: _site/file with spaces.html
Preparing to preview
Watching files for changes
Browse at http://localhost:3449/file with spaces.html
GET: /file (404: Not Found)
The reason is that the preview attempts to show http://localhost:3449/file with spaces.html
which is truncated to http://localhost:3449/file
instead of http://localhost:3449/file%20with%20spaces.html.
Switching between the two md files and previewing them seems to fix it for the rest of the session,
but after closing VS Code and opening the project again, etc., it occurs again.
Your environment
VS Code 1.95.3
Debian 12.8
Quarto check output
Quarto 1.6.39
[✓] Checking environment information...
Quarto cache location: /home/ca/.cache/quarto
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.4.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.46.3: OK
Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.6.39
Path: /opt/quarto/bin
[✓] Checking tools....................OK
Chromium: 869685
TinyTeX: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /usr/bin
Version: 2022
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.11.2
Path: /usr/bin/python3
Jupyter: (None)
Jupyter is not available in this Python installation.
Install with python3 -m pip install jupyter
[✓] Checking R installation...........OK
Version: 4.4.2
Path: /usr/lib/R
LibPaths:
- /home/ca/Store/R
- /usr/local/lib/R/site-library
- /usr/lib/R/site-library
- /usr/lib/R/library
knitr: 1.48
rmarkdown: 2.27
[✓] Checking Knitr engine render......OK
Activity
cderv commentedon Nov 28, 2024
@allefeld does
quarto previewoutside of VSCODE still works or also same issue ?Just to confirm where this should be fixed exactly.
allefeld commentedon Nov 28, 2024
quarto previewoutside of VS Code works, both without argument and with a filename.allefeld commentedon Nov 7, 2025
Could this issue please be looked at? I'm still stumbling over it, and have even disabled automatic preview in the VS Code extension, using HTML preview provided by another extension, which however works badly with Reveal.
Btw. it also happens if a space is not in the filename, but in a directory name.
I'm not sure whether this is a problem in Quarto CLI or in the VS Code extension. Happy to open an issue in
quarto-dev/quartotoo, if that helps?Currently on Quarto 1.8.25 and VS Code extension 1.126.0.
allefeld commentedon Nov 7, 2025
Command run by the extension in the "Quarto Preview" terminal:
Output in the "Quarto Preview" terminal:
"Quarto Preview" tab:
Clicking on the link in the "Quarto Preview" terminal successfully opens the file in a browser.
Running
quarto preview Open_Evening_2025-11-05.mdin a terminal outside of VS Code does the same.cderv commentedon Nov 10, 2025
This is Quarto VSCODE extension issue, and it seems related to
which was solved by
But not release yet I think. So testing can be done using the VSIX built as part of CI run.
For example,
And then manually install the VSIX to try it.
allefeld commentedon Nov 12, 2025
Thanks, that worked!
The other issue's description is correct in that the problem seems to only occur within multi-file projects.
Strangely, after installation of the VSIX file Quarto didn't find the right environment anymore (or any Conda/Mamba etc. environments), which I had to fix by setting
python.defaultInterpreterPath. Though I'm not sure that's directly related.mcanouil commentedon Nov 12, 2025
This is more likely related to the monthly update of VSCode and Python extensions (second Thursday of the month).