From 9ed7565fcb47d02e76398d41f24ba0817f6b9c2f Mon Sep 17 00:00:00 2001 From: Andrew Gallant Date: Sat, 25 Nov 2023 10:39:08 -0500 Subject: cli: error when searching for NUL Basically, unless the -a/--text flag is given, it is generally always an error to search for an explicit NUL byte because the binary detection will prevent it from matching. Fixes #1838 --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index afdbab2c..feaac274 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -34,6 +34,8 @@ Feature enhancements: Add new `--stop-on-nonmatch` flag. * [FEATURE #1814](https://github.com/BurntSushi/ripgrep/issues/1814): Flags are now categorized in `-h/--help` output and ripgrep's man page. +* [FEATURE #1838](https://github.com/BurntSushi/ripgrep/issues/1838): + An error is shown when searching for NUL bytes with binary detection enabled. * [FEATURE #2195](https://github.com/BurntSushi/ripgrep/issues/2195): When `extra-verbose` mode is enabled in zsh, show extra file type info. * [FEATURE #2298](https://github.com/BurntSushi/ripgrep/issues/2298): -- cgit v1.2.3