quarto-dev / quarto-dev/quarto

"Run Cell" won't work with cell under list item using a letter

Open
#393 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

I'm using using quarto with the vscode extension. When I have a python cell as part of a sub-list item and I run the cell, it attempts to run the whole cell along with the fenced code delimiter . Here is an example:

---
title: "Code Cell In Sublist"
format: typst
---

Here is a list with some code cells

1.  This is item 1. 

    a.  this is item 1.a

        ```{python}  
        # Run Cell doesn't work since ```{python} is sent
        print("Hello from item 1.a")
        ```

2.  This is item 2. 

    ```{python}
    # Run Cell works. ```{python} is not included
    print("hello from item 2")
    ```

quarto version: 1.4.550
quarto extension 1.111.0
jupyter extension 2024.2.0
windows 10

image

Note that this document renders perfectly with item 1a indented more than the code in item 2. It's just that the interactive portion isn't working.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the VS Code extension using the supplied Quarto document, focusing on the Run Cell action for a Python cell nested under a lettered list item. No source file or test is named; trace the Run Cell entry point and compare it with the working numbered-list case. Done means the nested cell sends only its Python body, without the fenced-code delimiter, while the existing case continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, python, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.