-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Ctrl+P fuzzy finder - no finding files when project folder on SFTP Drive #39493
Comments
FYI, turning off ripgrep fixed it for me... Now if only I had some idea why...
|
The fix above helped for me, but since GDrive is pushing users to switch to using Google Drive File Stream, being able to use VSCode over a mounted drive I imagine is even more important now. |
@ryanerwin Thank you !!! It worked like a charm. |
Sorry for not responding earlier. Let me know if you're still having issues. Also try the Remote-WSL extension if developing inside WSL. |
@roblourens Can confirm this is still and issue in Google File Stream 33, VS Code 1.39 and Mac0S Catalina(10.15). Also affects global find. Sublime finds files without issue with same setup. |
Ok, this is actually a duplicate of #69333 which had some investigation already |
Steps to Reproduce:
I saw some related posts that the fuzzy finder was slow over network drives, but using the fuzzy finder over a locally mounted drive from WSL shouldn't be too bad... Is there a configuration option to enable the fuzzy finder on non local drives or non NTFS drives?
I also backed up and removed the AppData/Roaming/Code folder to make sure it's not a configuration issue, but even with the default configuration, same behavior.
Reproduces without extensions: Yes
The text was updated successfully, but these errors were encountered: