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.
Currently Minus doesn't have any concept of lines. It only cares about the entire data being formatted according to the available number of columns (line number and highlighted search matches if applicable) and the original text data to minus.. Although it is quite simple for anyone to understand, but its not the most elegant and optimized solution.
For example we cannot do some of these effectively:-
This might be the first stepping stone to fix issues like #106 and other problems. Hence with screens API we introduce a new type
Screen
which not only brings in lots of performance improvements to the table but also gets a much more ergonomic API for applications to interact with the text data stored inside minus.This is very much a work in progress so much cannot be described about it but I will keep this updated as the feature furthur evolves