How does fuzzy find work?

[brandoncc]

I'm used to using Netrw, which I can search using / as a simple buffer. I don't understand why using / rarely seems to do anything in neo-tree, and even with it does something it always moves to something unexpected. I'm using astronvim and I'm not sure if that default config is making it act unexpectedly or if I just don't understand how to search the neo-tree buffer.

You can see in the video that I've attached that I am searching for "highlights" so I expected the cursor line to move to "highlights.lua", but it does nothing.

Thanks!

Screen.Recording.2023-02-08.at.10.25.26.AM.mov

[brandoncc]

I also just found filter_as_you_type and tried to map that to "/". The result is the same, I must be misunderstanding how it is supposed to work?

[miversen33]

Related: #721

Fuzzy search is undergoing a massive overhaul so at this time it's probably not worth addressing this thread as whatever information is discussed/provided will be out of date soon. At least not until said overhaul finishes testing and is deployed (I'd guess that will be in a few weeks, depending on what bugs are found during the testing phase).

[miversen33]

Fuzzy search != filter (though I understand how it can get confusing).

You can "search" your tree with either / (which does a search that is "called" fuzzy search, though its not as explained in #721 ), or f.

I have a feeling f (named "filter_on_submit") is what you are looking for.

[brandoncc]

Thanks, I understand the difference at a technical level. I called it fuzzy find because of the command name in the default mappings, sorry for the confusion.

I have tried f, /, D, and changing the command for "/" to filter_as_you_type. All of these have the exact same result....they do nothing! By any chance, did you happen to watch the video I included? I just can't imagine that what I'm experiencing is the intended experience.

[brandoncc]

Oh....I know what was happening now! Before I found f and D, and then posted this question, I found this issue and added this config, misunderstanding its purpose:

    find_args = {  -- you can specify extra args to pass to the find command.
      fd = {
        "--max-depth", "1",
      },
      find = {
        "-maxdepth", 0
      }
    },

I just removed this config and //f are working now. D still doesn't seem to do what I would expect, but this is much better. I think I must have been moving too fast so / didn't seem like it was doing anything before....thank you for the help!

[brandoncc]

Once I give D a little time, it also works. The "search as you type" is just slow (probably a debounce timeout, I'm guessing).

[miversen33]

Awesome! I'm glad you got it worked out :) Keep an eye on that PR, that should add much better fuzzy finding once its merged