-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Support for quarto's .qmd
file format
#12406
Labels
Comments
jtlandis
added
admin read
Pending admin review
enhancement
[core label]
triage
Maintainer needs to classify the issue
labels
May 29, 2024
Moshyfawn
added
design
[core label]
and removed
triage
Maintainer needs to classify the issue
labels
May 29, 2024
this would be awesome |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check for existing issues
Describe the feature
This request is largely similar in the same spirit to #5273 but for getting support for quarto
.qmd
. Currently, the only IDEs that provide the best experience with.qmd
are RStudio and VScode and it would be great to be able to interact with these documents in Zed.Quarto is the elevated version of
.Rmd
, which are like standard.md
documents, except that fenced code blocks may be executable and.qmd
supports more languages than justR
. Quarto is built on top of pandoc, which allows it to have a diverse range of output formats.Quarto is marketed towards the academic and scientific community. Given that zed has a pretty niche collaborative feature, it would be cool to collaborate with others through zed on
.qmd
documents.Practically speaking, the LSP and text highlighting may be fairly straight forward, as I believe markdown highlighting is supported and fenced code may be highlighted through some injection query? Due to my limited knowledge, the undertaking may be larger than I'm imagining.
I believe the language grammar for
.qmd
may be a modified version of.md
. Quarto has some special syntax involving cross referencing with@
and specifying pandocdiv
s like bellowlike in #5273, allowing output rendered into the text buffer may be another large undertaking.
If applicable, add mockups / screenshots to help present your vision of the feature
example view from RStudio
example view from VScode
The text was updated successfully, but these errors were encountered: