quarto-dev / quarto-dev/quarto-cli

echo and output options not working in manuscript companion notebooks

Offen
#8,680 7 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

enhancement manuscript
Vorherrschende Sprache
JavaScript
Sterne
6k
Forks
458
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
41

Beschreibung

Hi there,

Very excited about the new manuscript project type. I think I may have encountered a bug, however. I have a companion.qmd file with R code sitting alongside index.qmd. When I render the project with knitr and view index.html, the companion notebook is automatically displayed in the "Notebooks" section of the sidebar of my rendered index.md. So far, so good.

The problem is that output: false not echo: false in companion.qmd don't appear to be working, either in the YAML header or within individual code blocks. I set them to false and both the code and the code output still appear in the rendered companion.html file. (Note that this file has a blue bar at the top that says "Back to Article", it isn't rendered separately.)

output and false options work just fine in the index.md article, however. I'm using quarto version 1.4.549, using the VSCode extension (though I doubt that matters).

Apologies is if this is posted in the wrong repo! Would love any help I can get.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Start by rendering the reported companion.qmd alongside index.qmd with knitr and compare how YAML and code-block options are handled in the generated companion.html versus index.html. The fix is complete when echo: false and output: false work in the companion notebook, both in its YAML header and individual code blocks.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
r
Bereich
tooling
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.