Show more of available options for highlighting #32
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
Show default values for most cursorword settings and fg / bg colors to highlight - another use case of the plugin. Reference to underlying nvim api call which has even more options available.
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.
Hi @yamatsum,
I really like your plugin. It's simple and hasn't caused performance problems that I've come across with other cursorword plugins. It took me a while to realize it offered highlighting as well as underlining when I looked at the implementation and the docs for vim.api.nvim_set_hl. I thought there might be some value to other potential users by adding another example showing highlighting and the other options available.