There seems to be a bug (or a feature) regarding the results in a directory where ripgrep doesn't have permission to search. In my case I had a folder that did not belong to me inside my project and when I tried to search the files, it showed few results, varying the number of results shown. After running rg --files inside that directory, the results shown in snap where the ones found before running into a Permission denied message. There were some results after that message, but they didn't shown as well.
Adding --no-messages as argument shows the results as expected, but shows those files without permissions, which results in an error while selecting that entry: Error executing luv callback: ...re/nvim/site/pack/paqs/start/snap/lua/snap/common/io.lua:136: EACCES: permission denied:
My workaround to this moment was just changing the ownership of those files to me, but I think this deserves a better solution.
There seems to be a bug (or a feature) regarding the results in a directory where ripgrep doesn't have permission to search. In my case I had a folder that did not belong to me inside my project and when I tried to search the files, it showed few results, varying the number of results shown. After running
rg --filesinside that directory, the results shown in snap where the ones found before running into aPermission deniedmessage. There were some results after that message, but they didn't shown as well.Adding
--no-messagesas argument shows the results as expected, but shows those files without permissions, which results in an error while selecting that entry:Error executing luv callback: ...re/nvim/site/pack/paqs/start/snap/lua/snap/common/io.lua:136: EACCES: permission denied:My workaround to this moment was just changing the ownership of those files to me, but I think this deserves a better solution.