Issues with ripgrep finding files with no newline at end of text file about ripgrep HOT 2 CLOSED

You didn't provide a reproduction. Please provide one next time. I'll do it for you this time:

$ printf "foo\nquux\n" > haystack-with-trailing-newline
$ printf "foo\nquux" > haystack-no-trailing-newline
$ rg-13.0.0 -s -l '[^\n]\z'
haystack-no-trailing-newline
$ rg-14.0.3 -s -l '[^\n]\z'
haystack-with-trailing-newline
haystack-no-trailing-newline

The fact that that worked in ripgrep 13 was a bug. Anchors line \A and \z don't make sense with how you're using them because ripgrep is a line oriented searcher. There is no notion of "end of file." The only thing available to you is "end of line." And the logical model under which ripgrep operates is to search the contents of each line, and not the actual line terminators themselves.

The only way to have this work correctly is to enable multiline mode. In multiline mode, ripgrep is no longer line oriented, and treats the entire contents of each file as a single haystack. In that context, you can use anchors like \A and \z to mean "beginning of file" and "end of file," respectively.

In your case, you just need to add the -U flag:

$ rg-13.0.0 -l -U '[^\n]\z'
haystack-no-trailing-newline
$ rg-14.0.3 -l -U '[^\n]\z'
haystack-no-trailing-newline

from ripgrep.

Thanks for the clarification.

from ripgrep.