quarto-dev / quarto-dev/quarto-cli
Capture stderr with knitr engine like to match Jupyter engine output
Open
Nobody has claimed this yet.
engines-knitr
enhancement
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Render this doc. Where does the message go?
```{r}
cat("Hi!", file = stderr())
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by rendering the supplied R/knitr example and compare where its stderr message appears with the Jupyter engine's output. Trace the knitr rendering path to identify the handling of stderr; done means stderr is captured and displayed consistently with Jupyter output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100