New syntax about admonitions HOT 5 CLOSED

I've toyed around with implementing a custom syntax, but it is difficult to do. The biggest struggle is identifying what markdown content the user wants to be inside the admonition, and intercepting it from being rendered. An inline tag would work for very simple admonitions, but as they start getting more complex, the markdown blocks that Obsidian's markdown post processor sends to the plugin begin to be split up.

I may come back to this and keep trying to implement it, but for now until an update is released on Obsidian's side to enable alternate syntax, the setting added in 4.3.0 is the best I can do.

from admonitions.

Please see #18, this section of the ReadMe and this post on the Obsidian Forum.

Unfortunately this is a difficult problem to solve without an update on Obsidian's side. I attempted to hack it in using undocumented features of the API in version 4.3.0, but it is not perfect (see #36).

Until something is done by the Obsidian devs to make it easier to add internal links to the cache, this is probably the best I can do.

from admonitions.

I see. Thanks for your quick response!

What about inline Admonitions that renders after ::?

Can't the plugin identify this and return the rendered Admoniton for that line?

from admonitions.

Get it! You right. I don't know how to atract the community attention to this syntax problem. Is something really needed!

from admonitions.

@SubZeroX, please check out this section of the ReadMe.

from admonitions.