Subscript highlighted as strikethrough
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No file or test is named in the issue. Start by reproducing the subscript~1~ example in quarto-nvim and compare its highlighting with the Quarto Markdown reference; done means the subscript is no longer shown as strikethrough.
Written by the indexing model from the issue text.
Description
In quarto markdown format, subscript~1~ creates subscript₁
But in the syntax highlighting, is shown.
ref: https://quarto.org/docs/authoring/markdown-basics.html#text-formatting
- Dominant language
- Lua
- Stars
- 532
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from quarto-dev/quarto-nvim
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
quarto-dev/quarto-nvim#205 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
quarto-dev/quarto-nvim#127 · 4 reactions ·
-
enhancement waiting
Difficulty 3/5 1-2 days Newbie friendliness 25/100
quarto-dev/quarto-nvim#31 · 1 comment ·
-
add quarto-lspOpenenhancement waiting
Difficulty 5/5 Over a week Newbie friendliness 25/100
quarto-dev/quarto-nvim#13 · 3 comments · 1 reaction ·
All issues in quarto-dev/quarto-nvim
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
luainkernel/lunatik#1853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 3 days
-
Crash in ReaderFooter:setTocMarkers when the footer is disabledPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day