Add an option to apply the current scope highlight to the whole line #31
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
theHamsta
approved these changes
May 13, 2022
theHamsta
force-pushed
the
pr-hl_screenline
branch
from
d64ba1f to
1f4f0ee
Compare
auto-merge was automatically disabled
May 14, 2022 16:19
Head branch was pushed to by a user without write access
theHamsta
reviewed
Mar 20, 2023
| -- Highlight range [start_line, end_line) 0-based | ||
| local highlighter = function(start_line, end_line) | ||
| vim.api.nvim_buf_set_extmark(bufnr, current_scope_namespace, math.max(vim.fn.line "w0" - 1, start_line), 0, { | ||
| end_row = math.min(vim.fn.line "w$", end_line), |
Member
There was a problem hiding this comment.
please don't use functions that assume the current buffer for a function that explicitly takes a bufnr as an argument
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix: #12