Add optional leading whitespace highlighting capability #2583
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.
What is the purpose of this pull request?
Fixes #2573
Overview of changes:
Allows users to now optionally highlight leading whitespace, giving them more options when using MarkBind.
Users can now add an optional
+
after their highlight index specifier to indicate that the index should be inclusive of leading whitespace. For example previously1[:4]
would highlight theabcd
inabcd
. But now, by instead using1[:4]+
, MarkBind will highlightab
inabcd
(i.e. it will highlight the first 2 whitespace in the string).Anything you'd like to highlight/discuss:
Testing instructions:
Proposed commit message: (wrap lines at 72 characters)
Add optional leading whitespace highlighting capability
Checklist: ☑️
Reviewer checklist:
Indicate the SEMVER impact of the PR:
At the end of the review, please label the PR with the appropriate label:
r.Major
,r.Minor
,r.Patch
.Breaking change release note preparation (if applicable):