[[Bug]]: Pandoc-style fenced divs do not work as expected

[melff]

Thanks for this great plugin. Unfortunately, fenced divs do not work as expected:

1. The way they are supported is not consistent with the specification in the pandoc documentation. There, a fenced div that is started with something like ::: Example has to be closed with :::. The plugin currently ignores the closing fence.
2. Fenced divs are not visible in reading mode (=preview mode?)
   I'd be happy to provide a patch, yet I have not familiar enough with coding Obsidian plugins yet.

[kotaindah55]

Thanks for using my plugin and addressing some issues coming out of it.

I had be happy if I could consistently follow the implementation of Pandoc specification. But, unfortunately, this is beyond what I've been able to do so far. Briefly, what I'm doing here is extending what have been final-constructed in Obsidian. So, I cannot alter the builtin syntax that conflicted with the plugin syntax. For example:

::: fenced-div
This is fenced div
$$ The math-jax will continuously be parsed until it found it's closing delimiter.
:::
The colons above were parsed as math-jax content.
The end of math-jax syntax $$

::: another fenced-div
~~strikethrough
:::
still formatted with strikethrough~~

::: another fenced-div
Encounters code block
```
Technically, in editor mode, making the codeblock inside the fenced-div seems to be possible,
but not in the reading mode. Or, it will be such a complicated way to do so.
```
:::

Due to this behavior, I made a few changes to the syntax. It will only be closed if encountered different block context (i.e. codeblock, headings, etc), blank line, or the end of the document. So, the closing delimiter is no longer needed.

But, if you have a way to patch this, you can directly make a PR, or give the solving from this thread. I would be very glad to see this.

For the second issue, if I may ask you, which the part is not visible to you, the delimiter or the content? I will fix it as soon as possible.

[melff]

::: fenced-div
This is fenced div
$$ The math-jax will continuously be parsed until it found it's closing delimiter.
:::
The colons above were parsed as math-jax content.
The end of math-jax syntax $$

::: another fenced-div
~~strikethrough
:::
still formatted with strikethrough~~

I am not sure how to understand this example. Is it what consequences it would have if your plugin supported closing fences or is it a desired behavior? The example certainly is not correct Markdown syntax, so if your plugin would have problems with that it should not be an issue.

[melff]

For the second issue, if I may ask you, which the part is not visible to you, the delimiter or the content?

The delimiter and the content. I am using the "minimal" theme.

[melff]

But, if you have a way to patch this, you can directly make a PR, or give the solving from this thread. I would be very glad to see this.

That would be a challenge for me, as I lack experience with coding Obsidian plugins (I am more familiar with Python and R than with Typescript). But I'll see what I can do. 😃

[kotaindah55]

The example certainly is not correct Markdown syntax, so if your plugin would have problems with that it should not be an issue.

😅 I know that some of them don't seem to comply with the standard Markdown specification, e.g. CommonMark. But it is what happened in Obsidian. Because Obsidian itself doesn't come with the support of those syntax (fenced div etc). So, they will be treated as normal characters. And again, Obsidian doesn't give us a way to alter the internal parser.

Details

Editor mode (source mode)

Details

Preview/reading mode

[kotaindah55]

The delimiter and the content. I am using the "minimal" theme.

I tried running it with Minimal theme, but it seems to be normal to me. You can make the fences and the tag always be displayed via the setting by select "Both editor and preview" or "preview only" in "Always show fenced div tag" option. But, if it still disappear, you can provide me debug info of the app ("Show debug info" in the command prompt). I will try to fix it.

Details

Screencast.from.2025-03-11.04-43-48.webm

[kotaindah55]

That would be a challenge for me, as I lack experience with coding Obsidian plugins (I am more familiar with Python and R than with Typescript). But I'll see what I can do. 😃

No problem, it still useful if you have experienced with the Markdown parser. When I finished the other thread #3, I will make an attempt to include closing fences in the syntax.