feat(extensions): render-markdown.nvim nested block quote groups #182
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
|
Looks awesome 🙂 great to see all the hard work you’ve been putting in on this plugin. It’s been a staple in my config for a while now. Happy with the current implementation. Thanks for contributing! |
|
That was incredibly fast, thanks! I appreciate the kind words :) |
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.
render-markdown.nvim now supports setting block quote markers to highlights based on the nesting level of the particular marker.
Following commit 7051859 the default has also been updated to have highlights for 6 levels, but out of the box they all link to the same highlight.
Wanted test out how they would look with some colorschemes. LMK if you prefer a different coloring or you just want to keep the single color. I also made a more colorful version that I can push instead, but thought it might be a bit much haha.