Repository navigation
feat(rg): add encoding support - #1662
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 4f60c3e | Commit Preview URL | May 22 2026, 07:19 AM |
chaliy
added a commit
that referenced
this pull request
May 30, 2026
## What Add rg -E/--encoding support for auto, none, UTF-8, UTF-16LE, and UTF-16BE file decoding. ## Why Real ripgrep searches UTF-16 input when explicitly requested or when a UTF-16 BOM is present. Bashkit rg previously treated those files as lossy UTF-8/binary data. ## How Decode searched file bytes through rg-specific encoding handling before line splitting and binary detection, add parser/help/docs coverage, and extend real-rg differential cases for forced UTF-16, BOM auto-detection, and --encoding=none. ## Risk - Low - Only a narrow set of encodings is implemented; other WHATWG labels still return an unsupported-encoding error. ## Checklist - [x] Tests added or updated - [x] Backward compatibility considered
This file contains hidden or 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.
What
Add rg -E/--encoding support for auto, none, UTF-8, UTF-16LE, and UTF-16BE file decoding.
Why
Real ripgrep searches UTF-16 input when explicitly requested or when a UTF-16 BOM is present. Bashkit rg previously treated those files as lossy UTF-8/binary data.
How
Decode searched file bytes through rg-specific encoding handling before line splitting and binary detection, add parser/help/docs coverage, and extend real-rg differential cases for forced UTF-16, BOM auto-detection, and --encoding=none.
Risk
Checklist