quarto-dev / quarto-dev/quarto-cli
echo and output options not working in manuscript companion notebooks
Nessuno ha ancora preso questa issue.
- Lingua principale
- JavaScript
- Stelle
- 6k
- Fork
- 458
- Merge medio
- 1g 9h
- PR unite (30g)
- 41
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- r
- Ambito
- tooling
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100