-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Merge behave consistently #4042
Closed
Closed
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
5b098c3
implement consistent behaviour for highlight overlays
pascalkuthe ed3cdd3
Apply stylistic suggestions from code review
pascalkuthe 2c6f681
more elegant static dispatch
pascalkuthe c3f652f
remove unnecessary close from DiagnosticsOverlay
pascalkuthe 25427ce
move unwrap from helix-core to helix-term
pascalkuthe 1f26bca
move contents of overlay/tests.rs to overlay.rs
pascalkuthe 87f1a17
fixup overlay test documentation
pascalkuthe c2bdbbf
check overlay invariants
pascalkuthe 7ed579d
add missing assert
pascalkuthe File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old
map
s onHighlightIter
were doing two things:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have moved unwrapping the closure back into
helix-term
in 25427ce altough it make the code simpler if we simply returnedHighlightEvent
from theHighlightIterator
(panicking directly in the iterator) and then switched to a result once its actually required (because anunwrap
is required everywhere theHighlighterIterator
is used all call-sites will have to be changed in the future anyway). What do you think is betterIn
markdown.rs
the highlighting directly indexes into a string and therefore uses byte indices. Using char indices and translating back would be inefficient in that case so I am not sure there is a better solution right now.Rewriting the rendering to use byte indices seems to amount to translating byte indices to chars anyways so there might not be a better approach.