Skip to content
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

Emphasize extension options can be set globally in _quarto.yml #924

Closed
wants to merge 1 commit into from
Closed

Emphasize extension options can be set globally in _quarto.yml #924

wants to merge 1 commit into from

Conversation

coatless
Copy link
Contributor

Modifies the existing _quarto.yml to showcase how to set a global extension value for lightbox.

Follow up to the discussion in:

quarto-dev/quarto-cli#6968

Modifies the existing _quarto.yml to showcase how to set a global extension value for `lightbox`.
@coatless coatless changed the title Emphasize extension options can be set in _quarto.yml Emphasize extension options can be set globally in _quarto.yml Nov 17, 2023
@@ -70,9 +70,14 @@ format:
documentclass: report
margin-left: 30mm
margin-right: 30mm

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might not want to use lightbox as the example here as this is now built in to Quarto v1.4 (so in the future not likely to be recognized as an extension).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose the next option would be latex-environment; however, this lacks a single top-level key (e.g. values are set in environments and/or commands). What it be okay if I used a made-up extension?

I avoided the other extensions in quarto-ext/ since they were either: shortcodes with no global options (fancy-text, holder, and fontawesome), format-specific keys (attribution and pointer), or only had code cell level options to set (shinylive and include-code-files).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do think it is supposed to be generally understood that anything you can put in document yaml can be put in _quarto.yml. Therefore it might be more than good enough to just comment on the fact that this also applies to extensions (rather than use an example).

@cderv
Copy link
Collaborator

cderv commented Nov 20, 2023

/deploy-preview

Copy link
Contributor

@cwickham
Copy link
Collaborator

@coatless you haven't touched this PR in a while, are you still willing to edit it to focus on emphasizing that extension YAML can also be moved to _quarto.yml without including a specific example?

@coatless
Copy link
Contributor Author

@cwickham I think when I was trying different combinations I discovered a merge bug between _metadata.yml + _quarto.yml but ran out of time to raise an issue in quarto-dev/quarto-cli.

@cwickham
Copy link
Collaborator

So, perhaps we'll consider this PR stale and close it. Feel free to re-open if you want to pick it up again.

@cwickham cwickham closed this Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants