Support for built-in plotting devices (e.g. Quartz) removed in latest release?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- r, typescript, vscode
Research direction
Start at the Plot > Backend menu and the extension's plot-backend selection behavior introduced in version 3.0.0. Add an option for a built-in, non-integrated device such as Quartz, then verify that selecting it prevents automatic in-editor plotting without requiring quartz() in the R profile.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
First of all, huge thanks to all the developers for their efforts on this package! I've used it for years and it's head and shoulders above the RStudio experience.
My issue is that the latest update of the plugin (3.0.0) seems to have removed the option to use the built-in graphics device, defaulting to PNG/SVG if httpgd or jgd aren't installed and always creating new plots a pane in VSCode itself unless I explicitly call quartz() in the terminal. I personally really like the separate Quartz plotting backend and appreciate that creating a plot doesn't immediately take up a section of my IDE, but other than explicitly adding quartz() to my R profile I don't see any option to allow for this with the latest version of the plugin. Is there something I'm missing, or does the latest version force use of in-editor plot viewers unless you manually call a different plotting device?
Thanks in advance!
Describe the solution you'd like
An option in the Plot > Backend menu to use a built-in, non-integrated plot device.
Describe alternatives you've considered
Creating a manual override in my RProfile that explicitly sets the quartz rendering device, although this would cause the Quartz window to be opened immediately on launching R regardless of whether I've plotted anything.
Additional context
N/A
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 145
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 39
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from REditorSupport/vscode-R
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
REditorSupport/vscode-R#1785 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
REditorSupport/vscode-R#1687 · 4 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
REditorSupport/vscode-R#1815 ·
Maintainers usually reply within 1 day
-
bug confirmed
Difficulty 4/5 3-5 days Newbie friendliness 55/100
REditorSupport/vscode-R#1802 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
REditorSupport/vscode-R#1799 · 2 comments ·
Maintainers usually reply within 1 day
All issues in REditorSupport/vscode-R
Similar issues
-
check:failed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
iptv-org/iptv#53974 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
interledger/rafiki#3986 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day