I'm trying to search for files that include have text followed immediately by a line feed (\n) with nothing in between the text and the line feed (so ABC\n should return a match but DEF\r\n should not). Other files in the same path will have the ABC\r\n or the DEF\r pattern and I do not want to match them.
What I'm finding is that even when I turn off CR (by itself) as an EOL indicator in the configuration, the system will not match using \n (line feed) and I must still use \r (carriage return) to indicate the EOL (though they are not the same), and it is still returning a match to ABC\n when the item in question actually matches the pattern ABC\r\n.
Lastly, does the software as a whole use a different regular expressions engine than the tester? When I test all of the expressions described in the Regular Expressions Tester, my regex searches are working exactly as desired (with \n being treated as distinct from \r and with it not returning a match when I'm searching for ABC\n and the text being searched actually matches a pattern of ABC\r\n.
Am I missing something?