Feature Request: Improve command `Insert link` (Ctrl+K)

[jbridgy]

Feature Request: Improve command `Insert link` (Ctrl+K)

[RickStrahl]

If you embed a file that is more than a couple of levels removed from the current one, the link will be embedded as a fixed path. Arguably this should be a file://xxx/ path, but frankly that's not going to work any better unless the file exists in that path, so really that's a non-issue with a fully qualified physical path.

As to relative path embedding:

If you want relative paths you can add configuration into your root folder or the YAML header of the document that specifies a root path. More info here:

• Site Relative Override Path

When this is set MM searches up the hierarchy for files and uses that path as the / root folder for creating relative paths.

Otherwise, anything further back than 2 parent paths up from the current path is considered an absolute path.

Ultimately if you're working on a project that has 'root' you should add one of these marker files into the root folder of the project - that's the most reliable way to get clean project relative paths.

[jbridgy]

If you embed a file that is more than a couple of levels removed from the current one, the link will be embedded as a fixed path. Arguably this should be a file://xxx/ path, but frankly that's not going to work any better unless the file exists in that path, so really that's a non-issue with a fully qualified physical path.

The main issue is that command Insert link (Ctrl+K) of MM does not convert an absolute Windows file path to a relative URL whenever possible and probably most users strongly dislike doing this tedious conversion manually.
In the original post I forgot to point out that the behavior of Insert link depends on how the local file path is entered into the Link: field. There are two cases:

1. The local file path is entered directly by typing or pasting.
2. The local file path is entered indirectly by the ... button.

The example in the original post refers to case 1. In this case MM never converts an absolute local path to a relative one. After all it converts the spaces to %20 when you press the Paste Link button.

In case 2 the behavior of MM is better. It converts an absolute local path to a relative one if the directory of the current file contains the linked file.

So reconciling these two cases should actually be the first improvement.

When this is set MM searches up the hierarchy for files and uses that path as the / root folder for creating relative paths.

Otherwise, anything further back than 2 parent paths up from the current path is considered an absolute path.

Why do you restrict the conversion?
I suggest to make a file path relative whenever possible, that is as already mentioned above, relative to the current file if the linked file and the current file formally reside on the same volume. By "formally" I mean, that the linked file is not required to be existent when you create the link.
Maybe Insert link (Ctrl+K) should have an option like use absolute path to suppress the conversion in rare special cases.

Ultimately if you're working on a project that has 'root' you should add one of these marker files into the root folder of the project - that's the most reliable way to get clean project relative paths.

This route is MM-specific. Therefore it is impractical for my environment and presumably for most others.