Paths with space break the markdown parser

[rigmarole]

(I’m not a dev. I’m not evaluating your bug report. I’m just replying to a few points.)

@Gryom

inconsistency in space handling in path … and that seems inconsistent.

You linked to the help docs that explain this. Obsidian wiki links and Markdown links are not handled the same way. Markdown links need to be URL encoded.

@Gryom

And by the way, the following link produced by drag and drop of the image on a markdown file is incorrect too :

If you Ctrl-drag, you’ll get an absolute path to the image on your filesystem. If you drag, yes you get a relative path in the vault. That’s how Obsidian works. Relative filesystem paths is an open feature request, iirc.

---

I don’t know about every other point you made about compatibility. But here is a statement that WhiteNoise provided about compatibility issues. In particular, wikilinks are addition above Commonmark:

@WhiteNoise

Obsidian tries to stick to commonmark. Off the top of my head there are two additions (wikilinks and comments) and one difference (for performance, an HTML block must be contained in one markdown block). Other differences are due parsers bugs and will eventually be addressed.

If the incompatibility with other tools is due an Obsidian deviation from Commonmark, you can file a bug report and it will be treated as a bug.

If the incompatibility with other tools is due to other reasons, you can open a feature request and it will be voted/evaluated on a case by case basis.

And if you open a feature request, please search the forums first to make sure it doesn’t already exist.