mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #1145] Use markdownlint wirth quarto ".qmd" - files #2473
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#2473
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GitHubGeniusOverlord on GitHub (Mar 5, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1145
Hi,
is there a way to use this plugin on .qmd files?
Quarto https://github.com/quarto-dev/quarto-cli is a scientific publishing system based on markdown which allows executing code in between the markdown elements.
It would be absolutely awesome if we could make markdownlint work with quarto.
Example:
test.qmd
@DavidAnson commented on GitHub (Mar 5, 2024):
As a library, you can pass any file in and it will be linted. If you are using this library through one of the markdownlint CLIs, you can similarly specify "*.qmd". If you are using the VS Code markdownlint extension, you can tell Code to treat .qmd files as Markdown and they should automatically be linted.
@GitHubGeniusOverlord commented on GitHub (Mar 6, 2024):
Worked for me with the VS Code extension. It would be cool to mention this in the extensions documentation. Or possibly to set this property at installation time.
@GitHubGeniusOverlord commented on GitHub (Mar 13, 2024):
I have to correct: While VS Code can be taught to teach .qmd files as .md, this leads to the .qmd loosing its properties. For examples a cell in the .qmd cannot be run anymore. This renders this approach unusable at the moment.
@DavidAnson commented on GitHub (Mar 13, 2024):
As a request for linting non-Markdown files in the VS Code extension, this is a duplicate of: https://github.com/DavidAnson/vscode-markdownlint/issues/228