quarto-dev / quarto-dev/quarto

Possible conflict between Quarto extension and Dropbox causing corruption

Open
#538 5 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 experiencing a frustrating issue where certain actions cause unwanted changes to my Quarto documents in VSCode. Sometimes when I paste code into an R code block in qmd file or save the file, parts of the document will get changed or corrupted. This appears to occur only when both the Quarto and REditorSupport extensions are enabled. If just one of those two is enabled, I don't see the issue. It does not occur on every paste or save and I can't figure out what is the trigger aside from those actions. I presume it is related to code formatting.

As an example, here is a screenshot of a freshly created qmd file:

Screenshot 2024-09-13 at 09 49 23

And here is how it looks after pasting one line of code into the R code block:

Screenshot 2024-09-13 at 09 48 43

My setup:

  • VSCode 1.93.1
  • Quarto extension 1.114.0
  • R extension 2.8.4
  • Quarto 1.5.57
  • MacOS 14.6.1

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

Start by reproducing the corruption in a .qmd file with both the Quarto and REditorSupport extensions enabled, using the reported VSCode, Quarto, R extension, Quarto, and macOS versions where possible. Compare pasting into an R code block and saving with each extension enabled separately. Done means identifying the trigger and preventing unwanted document changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.