Relative path folder with "#" will show error "File names cannot end in dots or spaces" or generate new file

[tp1415926535]

Steps to reproduce

1. “New link format” set to Relative path to file in “Files and links” Settings .
2. create a folder named “C#”, and create a note named “Target” in the folder.
3. create a folder named “Other” , and create a note named “Test” in the folder:

[Target](../C#/Target.md)

4. create a note named “Test2” in root folder.

[Target](C#/Target.md)

The directory structure now looks like this:

│  Test2.md
├─C#
│      Target.md
└─Other
        Test.md

If you click the link in the Test.md, it will show error File names cannot end in dots or spaces.
If you click the link in the Test2.md, it will create a note named “C” in root folder.

Did you follow the troubleshooting guide? [Y]

Expected result

Relative paths should match files first, not the first ‘#’.

Actual result

it seems to be looking for the ‘/Target.md’ header inside the “C” note in the root directory, which doesn’t make sense.

Environment

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

RECOMMENDATIONS:
	none

[WhiteNoise]

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 note 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.

Also we don’t support filepaths with # in links.