Wrong example for `!relative` option about mkdocs

[oprypin]

Yes that is true. There's currently a problem with both examples. I actually ran into it just yesterday.

The 1st example has a bug that is fixed in facelessuser/pymdown-extensions#2206 but not released yet. But then it will run into the same bug as the 2nd example.

The 2nd example runs into a validation bug. Back when I was developing this, this line wasn't there yet: https://github.com/facelessuser/pymdown-extensions/blame/f4a66a6f06aa8e6f72f25fe6c579781f12e5636e/pymdownx/snippets.py#L85
Because this line is executed at load time and because mkdocs tries to validate the extension at load time, this fails.

mkdocs/mkdocs/config/config_options.py

Line 1020 in 8909ab3

# Confirm that Markdown considers extensions to be valid

Note that with the 2nd example only !relative is broken, !relative $config_dir still works.

[Andre601]

Note that with the 2nd example only !relative is broken, !relative $config_dir still works.

Okay. Sadly, this wouldn't be of use for me personally, as the !relative option would be most useful for me for translatable docs as I could have the snippet in the same relative position to the docs page instead of having X variants in the same folder...

Guess I'll have to wait for pymdown extensions to update.

[Andre601]

There seems to still be some issues with this option, even after 10.4 was released, which should fix it.

I mention this here, because I saw oprypin contributing the possible fix for this to the extension, so maybe he has further input on this.
Info on the issue, including currend markdown_extensions settings, is found here: facelessuser/pymdown-extensions#2236

[oprypin]

Yes I was saying there are 2 problems and only 1 is fixed.