quarto-dev / quarto-dev/quarto

Persist "Edit in Visual Mode" mode for Quarto documents regardless of save state

Open
#477 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps to reproduce the issue:

  1. Install the Quarto Extension
  2. Install the Quarto CLI standalone v1.4.557
  3. New File -> Quarto Document
    • Do not save the file.
  4. Click on the ... inside the editor with the Quarto document
  5. Notice a missing "Edit in Visual Mode"
  6. Save the file
  7. Re-click on the ... inside the editor with the Quarto document
  8. Notice "Edit in Visual Mode" is now present

What did you expect to happen?

I expected the listed options to be the same under the ... regardless of whether the file was saved or not.

VS Code
Untitled /Not saved
Quarto document file in VS Code that is not saved to disk and it's missing 'Edit in Visual Mode' option from `...`
Saved
Quarto document file in VS Code saved to disk and the 'Edit in Visual Mode' option is now present in the `...` menu
Positron
Untitled /Not saved
Quarto document file in Positron IDE that is not saved to disk and it's missing 'Edit in Visual Mode' option from `...`
Saved
Quarto document file in Positron IDE saved to disk and the 'Edit in Visual Mode' option is now present in the `...` menu

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

No source files or tests are named. Reproduce the issue with an unsaved Quarto document in VS Code and Positron, then trace the entry point that supplies the editor's ... menu. Done means "Edit in Visual Mode" is available consistently before and after saving.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
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.