feat!: add default colors for hover highlighting #194
Merged
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.
Hover highlighting is now enabled by default
(Hover highlighting is a feature currently requiring opt-in that was added in #180)
This works with the latest yazi when
use_ya_for_events_reading = true
is specified. To learn more about enabling this, see #152This will be the default behaviour when yazi 0.3 is released.
Hover highlighting colors no longer require manual configuration
autocolors-dark.mov
autocolors-light.mov
This change adds default colors for the hover highlighting feature. The logic supports both light and dark colorschemes:
The logic is borrowed from the
bufferline.nvim
plugin, which has a lot of users and is well-maintained. This also adds a dependency to bufferline.nvim, but as an optimization only its color utility functions are used as late as possible, and even they are only used when the user hasn't specified a custom highlight color.The optional
hovered_buffer_background
key in theYaziConfigHighlightGroups
has been renamed tohovered_buffer
. This change was made to better reflect the purpose of the key.To migrate, run this 🙂