-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Explorer Find: Support finding folders #230586
Comments
Does it work better for you if you unchecked the Fuzzy Match button? |
No, to me it worked better the old way, because it would turn out results, both folders and files (expanded only). PS: I don't find fuzzy search precise enough, I just selected as it should have found something, imho. |
Very surprised that you are not getting matches in that case.
|
I’m experiencing the same issue. The September 2024 update (version 1.94) makes the “Find in Explorer” function less usable, as it now searches only for files rather than both files and folders. I primarily use “Find in Explorer” to search for folders by name, so this change significantly impacts its usability for me. For now, I am reverting to the August 2024 update (version 1.93). @benibenj |
Adding comment here that 1.94 "Find in Explorer" seems broken and breaks an important way in which I could find and compare files by highlighted results. The current search either included only matched files or when fuzzy mode is enabled, it sort of highlights but also excludes non matching files. None of these options are currently usable and this seems broken. Reverting to 1.93.x until this is addressed or we are provided with a switch that enables use to choose between a highlight only or an include only behaviour. |
Any updates on this issue? I updated to version 1.95 to try out the new Copilot features, but I may need to revert if this bug hasn’t been fixed. I didn’t see any mention of it in the update notes. It significantly impacts the usefulness of the explorer since I typically use I also echo what @nazar says since the fuzzy match toggle controls both the fuzzy match AND the non-matches filter. @benibenj |
@luiul this is now available in 1.96 Insiders and will reach the general release (aka Stable) next month. Insiders can coexist with Stable. You can get it at https://code.visualstudio.com/insiders |
Hi, |
@alexandrupetrini You can set a shortcut for the commands: |
Then I have to say they are not mapped. I noticed this in 1.94. Thanks. |
Thanks for mentioning, should be fixed with this PR: #234193 |
Type: Bug
Steps to Reproduce:
Go to explorer, open search box
Write search pattern -> get no result.
I would rather need to disable this feature until it becomes stable.
Thanks!
VS Code version: Code 1.94.0 (d78a74b, 2024-10-02T13:08:12.626Z)
OS version: Linux x64 6.8.0-45-generic
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
webnn: disabled_off
The text was updated successfully, but these errors were encountered: