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

Quarto compatibility #180

Closed
RegisGourdel opened this issue Aug 11, 2022 · 3 comments
Closed

Quarto compatibility #180

RegisGourdel opened this issue Aug 11, 2022 · 3 comments
Assignees
Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch
Milestone

Comments

@RegisGourdel
Copy link

Hi, first thanks a lot for your work on this extension, it is the one thing that allows my VS code to still be more competitive than other solutions for LaTeX.

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Quarto documents have a specific file extension, qmd, meaning that it's not natively treated by LTEX at the moment. But the compatibility would make a lot of sense, and the parsing would probably be almost the same as for markdown files.

Describe alternatives you've considered
Two non-optimal solutions:

  1. Exporting the file tex file (in the process of exporting to pdf), browsing through the tex file with LTeX to find mistakes, and correcting in the original qmd file.
  2. Telling VS code to consider the original file as markdown, but then it has some syntax issues in particular with the yaml, and it needs to be changed back.

Additional context
So, Quarto is a recent pandoc-based solution that is very much between markdown and latex in terms of both syntax of capabilities, with easy conversion to both.
It's gaining popularity and I'm replacing some of my tex documents by this because it runs very nicely.

@RegisGourdel RegisGourdel added the 1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature label Aug 11, 2022
@sondalex
Copy link
Contributor

sondalex commented Sep 7, 2022

Hi, I have proposed a feature a draft PR few months ago #172 . I put this message here for anyone who would like to build on this draft and eventually enable [flexmark-java extension] (https://github.com/vsch/flexmark-java) in order to take care of pandoc's markdown special cases.

@valentjn valentjn self-assigned this Feb 12, 2023
@valentjn valentjn added this to the 16.0.0 milestone Feb 12, 2023
@valentjn
Copy link
Owner

Fixed via #172, thanks for the PR.

@valentjn valentjn added the 3-fixed Issue resolution: Issue has been fixed on the develop branch label Feb 12, 2023
@github-actions
Copy link

This issue is now fixed on develop. The fix will be included in the next release of LTEX.

If you don't want to wait, you can try out the nightly pre-release tomorrow. Nightly pre-releases are published every morning at around 4am UTC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch
Projects
None yet
Development

No branches or pull requests

3 participants