BSD grep is stricter about orphan tokens in -E mode #37
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.
Make sure to follow and check these boxes before submitting a PR! Thank you.
develop
branch.If you are using
WITH_BSD_GREP=yes
in/etc/src.conf
then iocell will fail, complaining like this:Which is due to stricter handling of orphan tokens in BSD grep's ERE compared to old grep.
Basically this
*/.foo
pattern is not compliant, and should be replaced by.*\.foo
.I've tested a number of commands against "old grep" iocell and not run into any issues. I believe I got all of the patterns. I checked for both
grepstring
andegrep ...
patterns.BTW I also kicked the https://iocell.readthedocs.io/en/latest/ build again, it's over a year since it was done. latest branch should be up to date now.