Output created but NO preview?

[DarvidTorres]

I'm running the Hello, Quarto tutorial for VSCode on Windows 10. It seems that everything's working, except that I see no preview. I checked the Quarto extension setting for "preview" to "internal" and checked the "reveal the preview panel..." as default. But I see no preview whatsoever. Here's my terminal:

PS C:\Programming\R\R Programming A-Z> quarto preview "c:/Programming/R/R Programming A-Z/hello.qmd" --to html --no-browser --no-watch-inputs

Starting python3 kernel...Done

Executing 'hello.ipynb'
Cell 1/1...Done

pandoc
to: html
output-file: hello.html
standalone: true
section-divs: true
html-math-method: mathjax
wrap: none
default-image-extension: png

metadata
document-css: false
link-citations: true
date-format: long
lang: en
title: Quarto Basics
jupyter: python3

Output created: hello.html

Watching files for changes

[cscheid]

You're using --no-browser, which instructs quarto not to open a web browser. So it doesn't. (I don't understand why you're not seeing the prompt which tells you the web server URL, though.) Try running without that option.

[DarvidTorres]

Thanks for answering! The --no-browser flag is the default option when rendering (and I don't know how to change it). Though there's no preview after runing it again without the option. There's no preview either rendering to PDF. Maybe it's a VSCode setting that I'm missing? I really want to preview my work within VSCode but don't know how

[cscheid]

I don't understand what's going on; on OS X, I can't reproduce your issue. @cderv, do you have any insights here?

[milanmlft]

Same thing happens for me on macOS, when I run Quarto preview through one of the VSCode shortcuts, it runs with the --no-browser and --no-watch-inputs flags.

[DarvidTorres]

The issue is that there's no preview panel in VSCode when I render the file.

This is what the tutorial page looks like:

This is mine:

The difference is that there's no preview panel in my vscode after rendering, even without the --no-browser flag and I don't know how to open that preview panel.

[cscheid]

It's definitely weird that you're seeing this. Any of these work for me:

• Shift-Alt-K shortcut
• Shift-Alt-P and then find "Quarto: Render" on the command bar
• Click on the render button on the .qmd tab:
  

Is it possible that some other VS code extension installed that is interfering?

[kenf1]

My output is different from what you have. (see screenshot below) There's a local host link I can open in browser in addition to preview panel.

• VS Code v1.74.2
• Quarto v1.59.0

[DarvidTorres]

Hi kenf1, can you tell me what's the command you're running? I'm using quarto preview "c:/folder/file.qmd" --to html as shown in the screenshots above, maybe you're employing a different flag? Thanks

[kenf1]

I have a keyboard shortcut in VS Code set to quarto.render. My quarto settings (in VS Code):

[DarvidTorres]

I have the same settings as you do and still can see the "Browser at ... " leyend after "watching files for changes" output.

[half-normal]

I was having this same problem after updating Quarto. A pre-existing quarto website would not render properly from the vs-code ctrl+shft+p commands nor the 'render' button. It would render correctly from the terminal, but preview would be sent to the browser. Meanwhile a new quarto website would render and preview correctly.

If this is the case for you, try deleting the _extensions, .quarto and _site/docs (i.e. the rendered website) folders and then reinstall the extensions. Now try rendering. This fixed the problem for me, but I'm not sure why.

EDIT: This happened again, deleting and reinstalling the extensions fixed it again. I wonder if this an issue with the fontawesome extension as this is the only one I am currently using.

[arthurgailes]

Also having this problem; it works fine in RStudio, and the localhost output renders in a browser, but the render on save function hangs as well.

Notes:

• if I force quit (ctrl+c in the terminal), then the internal viewer pops up, empty, and I get a successfully rendered message.
• it works fine with the external browser, including the render-on-save refresh

[allefeld]

This seems to be happening again. No problem until yesterday; I installed the newest Quarto version, but after that everything continued to work.

Today, opening the same folder & documents, and rendering via Ctrl-Shift-K, the internal preview does not open. In the Quarto terminal it says that the output has been created and I can browse it at a localhost address. But the "Rendering" message does not stop, and saving the document does not trigger a re-render. I can interrupt the rendering process via Ctrl-C in the Quarto terminal, but nothing happens but returning to the shell prompt.

Command created by the Quarto extension:

quarto preview <path>/test-document.qmd --no-browser --no-watch-inputs

VS Code 1.77.1, Quarto Extension 1.79.0, Quarto 1.3.313
Debian 11.6, kernel 5.10.0-21-amd64

Edit: This seems only to happen when a folder is open in which a Quarto extension is edited. Weirdly, editing & saving the _extension.yml file does lead to a re-render (but still no internal preview).

Edit 2: Ok, I think I figured it out. It happened for me when I was editing a Quarto format extension, but it's not really caused by that. I had created a document showcasing Pandoc & Quarto features, to test my Quarto format extension. Part of that was a Python code block which queried Quarto's built-in Pandoc for a list of the languages for which syntax highlighting is supported. Here is a minimal version:

```{python}
import subprocess

subprocess.run(['quarto', 'pandoc', '--list-highlight-languages'],  stderr=subprocess.PIPE)
```

Create a qmd file with this code block, and it should trigger the bug.

It seems that calling quarto in a subprocess, while it is already running from the VS Code Quarto extension, upsets things. If I directly call /opt/quarto/bin/tools/pandoc, it doesn't happen. If I call independently installed Pandoc, it doesn't happen either.

This is a rather exotic bug which will hardly affect anyone. Let me know if you'd like me to open a separate issue.

[stewartli]

inside of my vscode:

1. click render button -> no preview -> I guess no browser is the default.
2. key in terminal -> preview shows up.

[Kkhurana007]

I'm having the same issue.
Win 10 professional X64
IDE- Visual studio code
quarto version- 1.3.340

first, i rendered. The pdf gets generated, but does not open-

then, I previewed-

and got the following error-

Anybody, please help?

[cscheid]

It's the same error. Please confirm that you yourself can download it from an incognito window before trying to give me another link again.

[Kkhurana007]

kindly try with this one - https://github.com/Kkhurana007/fr_blog_mine/blob/main/posts/pythonic_thinking/Coding_Rules.ipynb

[cscheid]

It really is something with your pdflatex setup - quarto render Coding_Rules.ipynb --to pdf produces this for me:

[Kkhurana007]

I succeeded finally. I can see it in IDE, but the pdf doesn't open in Adobe or Microsoft's built-in pdf reader.

Any insights?

[cderv]

but the pdf doesn't open in Adobe or Microsoft's built-in pdf reader.

You mean automatically when doing a preview ? Or you can't open it when you double click on the file ?

[Kkhurana007]

when I double-click on the file. please see attached!
Coding_Rules.pdf

[cderv]

When I try to render the ipynb shared there: #3749 (reply in thread)

it works ok for and produce a PDF I can open outside of the IDE.

I don't know how yours got corrupted. You should check your LaTeX distribution that produce the PDF. Be sure it is up to date;

[Kkhurana007]

I think it has something to do with .yml settings. The LaTex files are up to date as the pdf documents work fine in other projects.

Here is the link- https://github.com/Kkhurana007/fr_blog_mine/blob/main/_quarto.yml

[cderv]

Also using this YAML for pdf format, I can render the document ok.

I also cloned you all repo and ran

quarto render .\posts\pythonic_thinking\Coding_Rules.ipynb

which successfuly produced a HTML file and a PDF file that I can open.

[Kkhurana007]

Perfect. I'll figure it out then. Many thanks for your time!