path extension and broken links

[s-cork]

I'm using the vscode implementation.

I noticed that:

• internal link autocompletion adds the path ending e.g. [foo](foo.md)
  • does it need to?
  • can this be configurable?
• detecting broken internal links only works if the .md extension is added
  • (add an internal link - break the link - observe detection of broken link. Remove the .md - observe no detection)
• detecting broken internal references doesn't seem to be a thing
  • (add an internal reference - break the reference - observe no detection.

[artempyanykh]

Thanks for asking @s-cork!

internal link autocompletion adds the path ending e.g. [foo](foo.md) does it need to? can this be configurable?

By default we add .md because with inline links it's not clear when something is a reference to a document inside the workspace or not, and having the extension helps to resolve this ambiguity.

Right now there's no config option for inline links to skip the extension, although it's also not hard to add.

detecting broken internal links only works if the .md extension is added

This is for the reasons explained above. Marksman is conservative when it comes to inline links; it will report a problem only when it's sure that the link should point to a file inside the workspace.

I'd imagine we could have a config option that would flip the behavior and assume that everything should be a link to a file unless it's a full URL.

detecting broken internal references doesn't seem to be a thing

Are you talking about [foo] kind of reference links? For them there's no detection because you generally can't say if [foo] is supposed to be a link or just some text in brackets. However, if you use a collapsed form of reference links e.g. [foo][] then Marksman will report diagnostics.

[s-cork]

detecting broken internal references doesn't seem to be a thing

It seems even with [foo][] and a definition of

## References
[foo]: foo.md

breaking the link doesn't cause any syntax highlighting

[artempyanykh]

@s-cork hm, is it VSCode?

[s-cork]

yes VSCode

[Lamby777]

Don't know if this is related or I'm just doing something wrong, but doing this:

For info on blah blah blah, see [Module 3](../xxxx/mod03.md)

gives a warning: 1. Ambiguous link to document '../xxxx/mod03.md' [1]

The only solution I found was doing that references thing they mentioned, but then I can't jump to the file using the LSP jump feature. Why is it considered ambiguous? I tried removing the .md, but that didn't work. I even tried using an absolute path, but that was even worse because it says the file just doesn't exist. I have multiple files in the workspace called mod03.md but they're in different folders... Why can't I just specify a path like this? ;-;