How can I sort workspace symbols so exact matches show up first

[IceSentry]

I'm trying to find a symbol named Material in this project https://github.com/bevyengine/bevy

There's a trait (interface) that matches exactly that but it doesn't show up at all unless I scroll down a lot.

This video shows what I mean

wezterm-gui_bB8E7rWLw9.mp4

It seems to match a bunch of letters first and I have no idea why. I'm using LazyVim with almost no modifications. The only modification I have for fzf-lua is this

return {
  "ibhagwan/fzf-lua",
  opts = {
    file_ignore_patterns = {
      "Cargo.lock",
    },
  },
}

To be clear, I don't always want exact matches, I just want to see them first

[ibhagwan]

It seems to match a bunch of letters first and I have no idea why. I'm using LazyVim with almost no modifications. The only modification I have for fzf-lua is this

You can tigger exact matching by prefixing with a tick 'foo, you can also play around with what shows up first using --tiebreak, read man fzf to sew which one fits best and add try it out with :FzfLua lsp_workspace_symbols fzf_opts.--tiebreak=…, see which scheme works best and set it up permanently under lsp.symbols.

[ibhagwan]

So, I tried using it directly with :FzfLua lsp_workspace_symbols and it doesn't even see the symbols I'm looking for.

IIRC LazyVim has some filters to show only certain types, try running a clean setup, fzf-lua only shows what the LSP can give it.

when I try to pass it the tiebreak option it breaks

What does it mean breaks?

Using 'foo also didn't seem to trigger exact matches in this window.

If you’re not seeing the results in the list to begin with exact matches won’t help the situation.

[IceSentry]

IIRC LazyVim has some filters to show only certain types, try running a clean setup, fzf-lua only shows what the LSP can give it.

I ran it as a separate command not through the LazyVim keybinds so I assume the default LazyVim filters weren't used since I didn't pass it any.

What does it mean breaks?

I tried it again and I think I probably had a typo or something because I don't get an error anymore. It still doesn't sort things like I would expect though. I tried setting it to "begin" so it would show the matches at the beginning first and the list was identical.

If you’re not seeing the results in the list to begin with exact matches won’t help the situation.

I am seeing the results, but only when using lsp_live_workspace_symbols, not with lsp_workspace_symbols. When using the _live_ version I can see the symbol, but if I do 'foo it doesn't show it

Here's a screenshot where I can see the Material interface showing at the bottom of the list. (and that's supposed to be using tiebreak="begin" too but it didn't seem to do anything)

Here's what happens if I search for 'Material. Nothing shows up.

[ibhagwan]

I ran it as a separate command not through the LazyVim keybinds so I assume the default LazyVim filters weren't used since I didn't pass it any.

The filters could come from the LazyVim defaults opts = {}, running the command manually doesn't bypass the filters unless you override the LazyVim opts.

I tried it again and I think I probably had a typo or something because I don't get an error anymore. It still doesn't sort things like I would expect though. I tried setting it to "begin" so it would show the matches at the beginning first and the list was identical.

These are the tiebreakers from fzf, fzf-lua has no control over these, if you believe it doesn't work as expected you can open an issue upstream (I personally don't see an issue in the tiebreaker algo).

I am seeing the results, but only when using lsp_live_workspace_symbols, not with lsp_workspace_symbols. When using the live version I can see the symbol, but if I do 'foo it doesn't show it

That's LSP dependent, some LSP's don't show everything and require a query to be sent (which is what the "live" version does).

Here's a screenshot where I can see the Material interface showing at the bottom of the list. (and that's supposed to be using tiebreak="begin" too but it didn't seem to do anything)

Not sure why this happens but this is out of fzf-lua's control, if you want exact matching you can type 'Material (note the tick prefix) or pass fzf_opts.--exact=true.

[IceSentry]

Not sure why this happens but this is out of fzf-lua's control, if you want exact matching you can type 'Material (note the tick prefix) or pass fzf_opts.--exact=true.

That's what I'm showing in my second screenshot. Adding the tick prefix made everything disappear. I tried a few other known exact symbols too and none of them show up when using the tick prefix.

[ibhagwan]

Not sure why this happens but this is out of fzf-lua's control, if you want exact matching you can type 'Material (note the tick prefix) or pass fzf_opts.--exact=true.

That's what I'm showing in my second screenshot. Adding the tick prefix made everything disappear. I tried a few other known exact symbols too and none of them show up when using the tick prefix.

Are you using the tick in the live version? You can only use it in fuzzy mode (non live).

Maybe your fzf version is bugged (I doubt it) or something LazyVim adds? It works as expected: