Image links containing spaces when represented in markdown format should be escaped

[cbz]

Steps to reproduce

Open a vault. Open settings. Under “Files and Links” turn off ‘Use Wikilinks’ so a markdown style link is created. Open a note, and drag in an image file containing spaces. Examine the underlying file.

Did you follow the troubleshooting guide? [Y/N]

Y

Expected result

The markdown link should be represented using the form:

[](<Path To File With Spaces>)

The angle brackets are used to escape a filename containing spaces by all markdown implementations respecting the common mark standard (can provide a link).

Actual result

The markdown will be represented using the form:

[](Path To File With Spaces)

Environment

---

SYSTEM INFO:
Obsidian version: v1.10.3
Installer version: v1.10.3
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

Additional information

[ariehen]

By default, the spaces are encoded as%20 in markdown links when you drag a file into a note. Is that not happening for you?

You can manually type and use <>, but Obsidian doesn’t add those in itself.

[cbz]

@ariehen

By default, the spaces are encoded as%20 in markdown links when you drag a file into a note. Is that not happening for you?

Encoding them this way in this particular context doesn’t seem to be compliant with how Markdown is being used elsewhere. See example 485 in the latest commonmark spec.

[ariehen]

URL encoded links (opposed to the bracketed ones) have been the type Obsidian creates from when I started using Obsidian.

Looks like there’s a FR here for an option:

Option to have arrow bracket escaping for markdown links

Use case or problem Hi, I was hoping to use Obsidian with my markdown notes, but it seems that the markdown links are URL encoded by default. Is there any way to configure Obsidian to use the Angle Bracket syntax ([Title](<file path with spaces>)) to have spaces in the source path by default? URL encoded source paths are really clunky and hard to parse at a glance. Or if there’s a plugin to do this for you already, please let me know (I couldn’t find one). I’d really appreciate it. Proposed …

---

I know the auto-updating of bracketed links was broken for a while:

`Update internal link` breaks links with angle brackets

Steps to reproduce Consider note Note.md: [Other note with space](<./Other note with space.md>) Rename Other note with space.md to Other note with space after rename.md Wait for auto update link if Automatically update internal links setting is on, or accept corresponding prompt. Did you follow the troubleshooting guide? [Y/N] Y Expected result [Other note with space after rename](<./Other note with space after rename.md>) Actual result [Other note with space after rename](Other%20n…

Support Internal links with markdown angle bracket syntax (especially rename)

Steps to reproduce Suppose there is a file, which contains space in it’s file name: demo image.png The first standard way to insert a file who’s name has space could be:  In this condition, with the right click, we can rename it directly: [image] The second way to insert it is more intuitive:  Obsidian can correctly preview it, but, with the right click, the renaming function disappeared: [image] Environment Opera…

^The second topic here looks like it may have been implemented/fixed (for the “shortest path when possible” setting, at least).

source mode | reading view

[WhiteNoise]

@cbz

The markdown will be represented using the form:

[](Path To File With Spaces)

When I drag and drop I get the version with %20, which is valid, not this.

For the rest, follow the link provided above.