No, you grep !
I recently1 discovered ugrep, and I have benefited a lot in using this to search my logseq journals. But recently I noticed I was getting fewer results and also confirmed some misses. My specific strange issue was that if I pointed directly to my miss, ug found it but not otherwise. I was consulting with microsoft copilot about this mystery. running into a weird ugrep issue where, ug -%% 'some blah' /some/foo/path , comes up dry , but if I am specific ug -%% 'some blah' /some/foo/path/more/specific/file.py , then I get results. Is there some index that needs to be poked for rebuilding? ...