Don't treat lines that start with 1 char as lists #71
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
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.
This fixes #70. I am surprised that this hasn't come up before, however, so I would love someone else to confirm that this doesn't break cases I haven't tested. Maybe I only noticed it because I have turned
textwidthback to my normal value.Part of the previous
formatlistpatregex doesn't appear to match what I think it should. Specifically this:[+-\\*]. That is supposed to match one of+,-, or*. However when I run that on my own vim v8.0, it does not. That double escape I think is supposed to become either[+-*]or[+-\*]. When I try to run it via/it doesn't match what I expect. I think that it is interpreting-as a range operator or something funky like that.This appears to correct the problem for me, though I haven't run it against your goldens.