VSCode: make "remembering" the language of the Insert Code Cell command configurable
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- tooling
Research direction
Start by tracing the VSCode Insert Code Cell command and reviewing the behavior introduced in issue #540. Determine where its language choice is handled and define the setting's default and prompting behavior; done means users can configure the choice while the current behavior remains the default.
Written by the indexing model from the issue text.
Description
Apologies for not raising this when issue #425 was discussed a few weeks ago! I understand that for most teaching contexts (probably most contexts overall, tbh), the change implemented in #540 (switching from always prompting a language to assuming the same as another, previously used code cell) is desirable and a good default.
In my case, I write a lot of mixed R/OJS Quarto docs and would appreciate the ability to restore the previous behaviour (though I don't wish to impose it on anyone else!). Having to constantly change {r} to {ojs} because I used a single R chunk at the top of the doc discourages me from using the command at all. If it's possible to make this on option that is set to the new behaviour by default, that would be fantastic!
I'd also love it if the code cell snippet had a label option pre-populated, but maybe that's being greedy 😛
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
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
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
quarto-dev/quarto#1099 ·
-
vscode
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
quarto-dev/quarto#934 · 1 comment · 2 reactions ·
-
vscode
Difficulty 5/5 Over a week Newbie friendliness 42/100
quarto-dev/quarto#1130 ·
-
vscode
Difficulty 3/5 1-2 days Newbie friendliness 68/100
quarto-dev/quarto#1122 ·
-
bug vscode zotero
Difficulty 4/5 3-5 days Newbie friendliness 48/100
quarto-dev/quarto#1119 · 1 comment ·
All issues in quarto-dev/quarto
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
vercel/vercel-plugin#199 ·