quarto-dev / quarto-dev/quarto-cli

Inline code returning empty string not rendering correctly

Open
#13,185 6 comments 0 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Aug 5, 2025.

bug engines-jupyter
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

Inline code which evaluates to an empty string is rendered as the contents of the inline block (the code, not the evaluation).

Steps to reproduce
---
title: "Reproducible Quarto Document"
format: html
engine: jupyter
---

`{python} ""`

Actual behavior

Reproducible Quarto Document
{python} ""

Expected behavior

Reproducible Quarto Document

Your environment
  • IDE: VS Code
  • OS: Windows 10
Quarto check output

Quarto 1.7.32
[>] Checking environment information...
Quarto cache location: ...\AppData\Local\quarto
[>] Checking versions of quarto binary dependencies...
Pandoc version 3.6.3: OK
Dart Sass version 1.85.1: OK
Deno version 1.46.3: OK
Typst version 0.13.0: OK
[>] Checking versions of quarto dependencies......OK
[>] Checking Quarto installation......OK
Version: 1.7.32
Path: C:\Program Files\Quarto\bin
CodePage: unknown

[>] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)

[>] Checking LaTeX....................OK
Tex: (not detected)

[>] Checking Chrome Headless....................OK
Chrome: (not detected)

[>] Checking basic markdown render....OK

[>] Checking Python 3 installation....OK
Version: 3.10.11
Path: .../python.exe
Jupyter: 5.7.2
Kernels: python3, ir

[>] Checking Jupyter engine render....OK

[>] Checking R installation...........OK
Version: 4.3.1
Path: C:/PROGRA1/R/R-431.1
LibPaths:
- .../4.3
- .../R/R-4.3.1/library
knitr: 1.46
rmarkdown: 2.26

[>] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.