Paths with space break the markdown parser

[CawlinTeffid]

I agree it’d be nice if Obsidian handled spaces in Markdown link paths more gracefully, and others would like it too (see for example this closed feature request: Reconsider requirement for markdown links to be urlencoded).

@Gryom

First yes I did use the search button with image and path and did not see anything relevant in the first 10 or 15 hits.

Try something with “space” or “spaces” in it (spaces path, space link), since that’s central to the problem.

@Gryom

Moreover having to escape spaces when typing common mark links but not when typing wiki links is inconsistent as a user experience, and it is annoying and slowing entry down.

Unfortunately they’re inconsistent in general (for example you add an alias to the front of one and the back of the other). This is at least partly because they’re preexisting syntaxes that were made for different purposes.

@Gryom

Its only advantage is the plethora of engines that parses it, its simplicity for direct user entry and the fact it can be a lightweight common file format.

That’s 3 advantages , and they’re not small ones.

@Gryom

On a more general note, Markdown is not a great semantic/rich text format, … and commit the same cardinal sin as HTML

It wasn’t designed to handle everything — it’s a light markup for writers, with HTML as a fallback. Like HTML, it’s flawed but has historical momentum. This is the imperfect world we live in.