fix(cli): Ignore (do not abort on) non-utf8 files when walking recurs… #167
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
…ively Previously a hard error, but safest bet seems to ignore. Ripgrep handles binary data with NUL byte detection, which does not seem necessary here Closes #166
alexpovel
force-pushed
the
binary-data
branch
from
032f3ef
to
9190e55
Compare
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.
…ively
Previously a hard error, but safest bet seems to
ignore. Ripgrep handles binary data with NUL byte
detection, which does not seem necessary here
Closes #166