This repository has been archived by the owner on Mar 31, 2021. It is now read-only.
Render non-fuzzy links without content correctly #11
Conversation
This file contains 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
Currently a link like `[[https://example.com]]` gets rendered as `<em>//example.com</em>`, which is not the expected behaviour. The current behaviour is retained for "fuzzy" links I.E. without a protocol, which seems to be what is intended, but fixed in all other cases.
C-xC-c
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi!
First, thank you for making this package, it's really great!
Currently, proper links without contents, e.g.
[[https://example.com]]don't render quite how you expect, #9 gives a full example. This adds an extra case when formatting links to handle the above case properly.Fixes #9.
Thanks again~