Skip to content

Fixes bug where usage parsing fails on multiple blank lines. #109

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

Closed
wants to merge 1 commit into from

Conversation

ttuggle
Copy link

@ttuggle ttuggle commented May 1, 2019

A tiny change to the regex allows multiple blank lines to appear in the usage string.

@jaredgrubb
Copy link
Member

Can you provide a sample that fails and should pass? I want to test it against the Python one for conformance. (Also, that sample would then make a great unit test).

@ttuggle
Copy link
Author

ttuggle commented May 2, 2019

Actually let me close this out until I can test it further. This fix was originally made last year on Linux on an air-gapped network… I forget the exact way I was seeing the bug, and upon testing now, it looks like this change may introduce bugs of its own, at least on Mac.

Sorry for the trouble. I'll create another pull request if I can get this nailed down and tested. What Windows compilers do you test on?

@ttuggle ttuggle closed this May 2, 2019
@jaredgrubb
Copy link
Member

I can't recall ... I dont have Windows machines myself, though others have tried it. The README states some of the compilers that we supprot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants