-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global cell defaults #173
Global cell defaults #173
Conversation
Allow user to define code cell defaults in yaml
Add a cell option for editor-font-size. You might perhaps want a different name?
@ute so, I removed the I've added a demo document in If you're okay with the changes, please let me know and I'll merge it in. Otherwise, if there are changes you think should be made, please go ahead and let me know when I should re-look at the PR. Thanks again for submitting a PR and the discussion! 🎉 |
Thank you, James, and great documentation 💯 🎉 ! As for the yaml key: you came up with some nice suggestions for the name |
@ute I'm inclined to keep it at Maybe we should opt for:
|
From pinging the internet, we have:
|
I am not on mastodon (👍for asking the public voice) but I've read |
@ute I thought about that a lot (c.f. the Viewing any non-RStudio documentation entry for the getting started: https://quarto.org/docs/get-started/hello/vscode.html#code-cells Vs. RStudio entry: https://quarto.org/docs/get-started/hello/rstudio.html#code-chunks The computation block switches to https://quarto.org/docs/computations/r.html#code-blocks So, in VS code it shows: ![]() But, in RStudio we have chunks: ![]() I'm partial to go more towards |
I am also mainly using vs code now - lets go for cell options then. You need not take consideration of me, though. It is you who develops the package, and I can see you put a lot of thought into syntax and documentation 😊👍 |
c5a55c2
to
0d120b9
Compare
…arto-webr into user-defaults-and-editor-fontsize
@ute thanks for the kind words! I've updated it from Thanks again for the PR 🎉 |
Here is the pull request for my feature suggestion, #172
It is just a proof-of-concept, maybe it can be solved in a very different way, or you even have planned something more general.
(sorry, I am really clumsy at GitHubbing ;-))