Support for plain markdown links #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support Standard Markdown Links
Obsidian:
[[Link#Anchor|Custom Text]]Markdown:
[Custom Text](Link)With obsidian style I can write
[[Conecpt]]if I want to link the 'Concept' page. mkdocs-obsidian-bridge plugin will handle everything else. Please have a look into the README file there.With this PR we could get work it in plain markdown. Links would look like:
[Concept](../Concept).Files in the same directory can be accessed by
../and files in one directory by../../and so on.limitation: Using
.mdto reference the real file is not supported and will not work.refer #9