From 46f94826fdb6e3061362ac975cb18edc8c98c30a Mon Sep 17 00:00:00 2001 From: Andrew Gallant Date: Tue, 14 Mar 2017 08:22:37 -0400 Subject: [PATCH] Update whirlwind tour with encoding info. Fixes #1 --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index c8d0c4cc..5cae9049 100644 --- a/README.md +++ b/README.md @@ -230,11 +230,10 @@ colorize your output and show line numbers, just like The Silver Searcher. Coloring works on Windows too! Colors can be controlled more granularly with the `--color` flag. -One last thing before we get started: `ripgrep` assumes UTF-8 *everywhere*. It -can still search files that are invalid UTF-8 (like, say, latin-1), but it will -simply not work on UTF-16 encoded files or other more exotic encodings. -[Support for other encodings may -happen.](https://github.com/BurntSushi/ripgrep/issues/1) +One last thing before we get started: generally speaking, `ripgrep` assumes the +input is reading is UTF-8. However, if ripgrep notices a file is encoded as +UTF-16, then it will know how to search it. For other encodings, you'll need to +explicitly specify them with the `-E/--encoding` flag. To recursively search the current directory, while respecting all `.gitignore` files, ignore hidden files and directories and skip binary files: