Critic markup

Use case or problem

Since I use obsidian equally for making notes as well as reading them and intend to use mobile app just as a reading and learning tool, it would be great to have more options in including critic markup mode(apart from the highlight syntax)

Proposed solution

I use Ulysses to draft my essays to publish them on the blog and I really enjoy their version of markdown (markdownXL?) which have options such as

||delete|| ::highlight:: {Annotation} and ++comment++ and %% for comment block

Even the {{foobar}} syntax of roam blocks or iawriter TOC is unused right?

This small change will absolutely be immensely helpful!


%% can be used as comments in Obsidian as well

Due to its flexibility, Obsidian already suffers from the fact that too many new “language elements” are introduced without thinking too much about the side effects. This makes it increasingly less compatible, and we start to build a locked-in platform—again.

I still think “critic markup” might find its use cases, but there is already a version out there, so why not adopt its syntax? And maybe make it a plugin (be it core or community), so users can make their own informed choice?

In short, Critic Markup uses this basic syntax:

  • Addition {++ ++}
  • Deletion {-- --}
  • Substitution {~~ ~> ~~}
  • Comment {>> <<}
  • Highlight {== ==}{>> <<}

which should be enough to successfully copy edit text.



This! I‘ve also argued for CriticMarkup here:


Yep, read that. Totally agree. Critic Markup support would be nice for us writers! (Maybe even with an “Accept/Reject” feature? From the toolkit they offer, it should be easily adaptable, I think …)


+1 bump-ski! Plez

Any updates?

1 Like

A strong upvote for adding Critic Markup support to Obsidian. Markdown won’t have a prayer of competing with .docx files in organizations, enterprises, and academia without this feature, and it would be equally useful for annotating one’s own notes and writing.

1 Like

Oh wow!
I am just beginning to have a look at critic markdown but am beginning to think this might be at least part of a potential solution to what I proposed here:

I even left out change tracking as I found the post would get too long but it is something I very much wish for.

Versioning can to some extent be done manually (I make copies of the evolving file adding 1.0, 1.1 etc. and continue to work on my main file. But this is not a replacement for anything that truly tracks the changes a text goes through over time.

Also, it would open doors towards collaboration, somerthing I also would like to see very much…

Thank you for pointing me in that direction. And:

I was just thinking along the lines of having the changes saved in a separate file so as to not clutter the text itself.
This file could be hidden in the file browser and its content only be displayed in the main file upon specific user request. Maybe a specially adapted form of transclusion would be something to consider.
But I am a total programming noob, so please forgive my stumbling when it comes to suggestions. They originate from a sole user perspective.

I’m surprised that Obsidian still doesn’t support Critic Markup, either by default or plugin. It’s such a basic and important feature.

I second this- hopefully with interesting views for comments (like showing a counter on the gutter besides the main text, hovering on it showing the comment)