danielfalk
sometimes it still finds ignored files
I have installed this recently and it mostly works great. I have not changed the default config, but still I see files from .git folders from time to time:
Any idea why this happens?
One way it might happen is if those files have gotten in your history. The files come from 2 sources: the history and the filesystem via recursive scan. If they're not in your history (looks unlikely in this case), then it would be related to the patterns that are passed into ripgrep as command line arguments. Maybe there should be some way of turning on diagnostics to be able to see the resulting command, but putting in a temporary print() could do it.
oh, I think it might be your ignore_patterns config. There are a lot of default ignore patterns, which should prevent extraneous entries like this. If you're overriding this setting, then that might explain it.
Are you still seeing this issue? If so, can you see if using the default ignore patterns fixes it?
I'm also experiencing this issue. One of my folder (.direnv with some Python venv in it) is shown even though the folder has always been git-ignored in the repository it lives in. After looking at the SQLite database, it indeed has entries for files in that folder.
I've tried to understand how it could happen and on a fresh database: went to the parent folder, opened smart-open which returned the .direnv files because it's not in the folder that's ignored, then moved to the child folder and opened smart-open again, and indeed the ignored files were there, even if I didn't opened them in the previous step.
