New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entering a full path in quickopen matches gitignored files, but not search.excluded files #41495
Comments
Since I see the label "file results", this seems to be an issue with the RipGrep matching and not with the fuzzy scorer of quick open that is only used for sorting purpose as far as I know. |
Are those files covered by a gitignore pattern? It now skips gitignored files by default. You can disable this with If that's not it, do you see any pattern to which files it can't find (besides "recently opened" files, which are searched differently) |
It does appears the issue was related to |
I do see that - when you enter a full path like that, it matches immediately and bypasses the actual search that's looking at the gitignore file. But this is inconsistent with |
Absolute paths and paths from a root folder should always match, ignoring the |
Ok. Seems like that doesn't work for .exclude settings anymore, I guess that's the bug. |
This should now work consistently for absolute paths but not relative paths, by design. |
It's hard to identify the exact circumstances that trigger this, but starting from some recent version (either 1.18 or 1.19), quick open began consistently missing files that it should clearly match. This seems to happen most particularly in large repositories with many files.
To illustrate here is a screen recording of an obvious case:
The text was updated successfully, but these errors were encountered: