We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
>
Describe the bug
In Obsidian, both of the below ways of defining a callout with multiple lines work, not in quartz:
> [!note] Line Anotherone > [!note] >Line >Anotherone
Expected behavior
The callout should only stop after an empty newline, not requiring > on every line. The same goes for nested callouts:
> [!note] Outer Outer > > [!note] Inner > > Inner >Inner > >Outer
It would be nice to have a core plugin to enable this Obsidian markdown feature, even if it is not markdown standard, as with other features.
Desktop (please complete the following information):
node
npm
Additional context
The following transformer fixes it (not extensively tested yet):
import { QuartzTransformerPlugin } from "../types" export const CalloutNewlineFix: QuartzTransformerPlugin = () => { return { name: "CalloutNewlineFix", textTransform(_ctx, src) { if (typeof src !== "string") { src = src.toString() } return src.replace( /^> \[!(\w+)]\s*\n((?:[^>\n][^\n]*\n?)+)/gm, (_match: string, type: string, content: string) => { const fixedContent = content .trim() .split("\n") .map((line) => `>${line}`) .join("\n") return `> [!${type}]\n${fixedContent}` }, ) } } }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
In Obsidian, both of the below ways of defining a callout with multiple lines work, not in quartz:
Expected behavior
The callout should only stop after an empty newline, not requiring
>
on every line.The same goes for nested callouts:
It would be nice to have a core plugin to enable this Obsidian markdown feature, even if it is not markdown standard, as with other features.
Desktop (please complete the following information):
node
Version: v22.11.0npm
version: 10.9.0Additional context
The following transformer fixes it (not extensively tested yet):
The text was updated successfully, but these errors were encountered: