quarto-dev / quarto-dev/quarto-cli
`julia` engine: include cell label in progress messages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
Both the knitr and jupyter engine include cell labels in their output when running quarto render. It would be nice if julia did the same.
Steps to reproduce
Here's file with a code cell that has a label set:
---
title: "Untitled"
format: html
engine: julia
---
```{julia}
#| label: addition
1 + 1
```
Expected behavior
For example, something like knitr output:
processing file: r.qmd
1/3
2/3 [addition]
3/3
output file: r.knit.md
Actual behavior
Code cells are numbered but don't add the label (I do appreciate the line number in the output!):
quarto render julia.qmd
Running [1/1] at line 7: 1 + 1
Your environment
- OS: Mac Sequoia 15.0
Quarto check output
Quarto 1.6.21
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.4.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.46.3: OK
Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.6.21
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: v2024.03.13
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/charlottewickham/Library/TinyTeX/bin/universal-darwin
Version: 2024
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.12.2
Path: /Users/charlottewickham/.pyenv/versions/3.12.2/bin/python
Jupyter: 5.7.2
Kernels: julia-1.10, ark, python3
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........OK
Version: 4.3.3
Path: /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources
LibPaths:
- /Users/charlottewickham/Library/R/arm64/4.3/library
- /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
knitr: 1.45
rmarkdown: 2.28
[✓] Checking Knitr engine render......OK
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 tracing the Julia engine's progress output and comparing the existing knitr and jupyter handling described in the issue. Done means a labeled Julia cell such as addition includes that label in quarto render progress output while unlabeled cells retain their current numbering and line information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100