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, here's my attempt at adding explicit support for mini.nvim.
I started by patching
mini.pick
andmini.files
which are unusable onmaster
(the colours for selected and unselected items are the same, making it impossible to tell what's selected). I then decided to add support for the rest of the plugins.As a user of many of the mini.nvim modules, I tested the changes by running the fork locally.
When there was ambiguity, I took inspiration from how other themes have added support for mini.nvim and how other plugins have been supported via melange.
I appreciate this is a large PR and is difficult to test given the scope of mini.nvim, so please let me know if there is anything I can do to help with the review process!
Here are some screenshots of my nvim setup showing how mini.pick, mini.file, and mini.diff look respectively.
Closes #95.
Checklist for Plugins
Paste link to documentation listing highlight groups:
colors/melange.lua
) Add highlight groupsREADME.md
) Add link to plugin source repository