mirror of
https://github.com/BurntSushi/ripgrep.git
synced 2025-08-04 21:52:54 +02:00
remove redundant words
This commit is contained in:
@ -104,7 +104,6 @@ give you a glimpse at some important downsides or missing features of
|
|||||||
* If you need to search files with text encodings other than UTF-8 (like
|
* If you need to search files with text encodings other than UTF-8 (like
|
||||||
UTF-16), then `ripgrep` won't work. `ripgrep` will still work on ASCII
|
UTF-16), then `ripgrep` won't work. `ripgrep` will still work on ASCII
|
||||||
compatible encodings like latin1 or otherwise partially valid UTF-8.
|
compatible encodings like latin1 or otherwise partially valid UTF-8.
|
||||||
`ripgrep` may grow support for additional text encodings over time.
|
|
||||||
`ripgrep` *can* search for arbitrary bytes though, which might work in
|
`ripgrep` *can* search for arbitrary bytes though, which might work in
|
||||||
a pinch. (Likely to be supported in the future.)
|
a pinch. (Likely to be supported in the future.)
|
||||||
* `ripgrep` doesn't yet support searching compressed files. (Likely to be
|
* `ripgrep` doesn't yet support searching compressed files. (Likely to be
|
||||||
|
Reference in New Issue
Block a user