Note created from relative link lands in root

[pjeby]

Steps to reproduce

In a subfolder within a vault, insert an explicit relative link [[./x/y]]. Hover-preview the link and click to open it, or use the open link under cursor command.

Expected result

A note x/y.md is created in a subdirectory of the folder the note is in, and the note is opened

Actual result

The operation silently fails after creating x/y.md under the vault root.

Environment

• Operating system: Windows
• Obsidian version: 0.12.19

---

Additional information

It doesn’t matter what the link creation setting is set to.

[WhiteNoise]

Thanks.

This is part of broader issues/not yet implemented features around relative links (especially important with standard markdown links in relative path mode).

In relative path mode, always add `./` and `../` in front of links

In relative path mode, always add ./ in front of links for files in subdirectories relative to the current file and ../ for files in subdirectories above the current file. This is particularly important since Obsidian doesn’t use a front / in absolute path mode and this creates confusion and ambiguity.

Obsidian has trouble creating new notes from "Relative path to file" links

Steps to reproduce Set “New link format” in File preferences to “Relative path to file.” Create a new link with a relative format (this has to be done manually, as the file doesn’t exist yet so Obsidian can’t guess your desired folder path. E.g., ../Calendar/20200803 Try to create a new note from the link Cry Expected result Successful creation of the new file in the expected directory. Actual result An ENOENT error. Environment Operating system: macOS 10.15 Obsidian version: 0.…

Broken links in relative path mode on move/rename

In Relative-path mode, relative links should be updated when: a linked file is moved (done!) AND a file that contains the link is moved (to-do!). EDIT: Added minimal example: Have foo.md and bar.md in the root of the vault. With foo.md containing [[bar]] move foo.md to /subdir Expected foo.md content: [[../bar]] Actual [[bar]] Same problem applies to standard markdown links.

and some others