Quick fzf-lua window when there's only one result

[hb0nes]

When doing something like go to definition or go to type definition

      vim.keymap.set("n", "gD", fzf.lsp_typedefs)
      vim.keymap.set("n", "gi", fzf.lsp_implementations)

I see a quick pop-up and then it disappears and does its thing. There's some delay there and it's jarring/ugly.

Is it a misconfiguration on my side or inherent to fzf-lua?

Any idea how I could prevent the pop-up if there's only one result?

[ibhagwan]

LSP calls are asynchrony by default (to prevent hangs on slow LSP servers), when async we must open the interface fkrdf and wait for results, set lsp.async=false and lsp.jump_to_single_result=true to make it sync and jump immediately when only one result is found.

[hb0nes]

For me, it was enough to set lsp.jump_to_single_result=true
Maybe this can be set as default?
I don't see it in the README.md and it improves the UX for me.

❯ rg -l jump_to_single_result
lua/fzf-lua/win.lua
lua/fzf-lua/utils.lua
lua/fzf-lua/providers/lsp.lua
lua/fzf-lua/profiles/telescope.lua

Of course, if could have some sort of performance or other implication that I don't know about.

edit: I was mistaken. Setting async = true explicitly indeed, as expected, still gives me a microsecond popup.

[ibhagwan]

Maybe this can be set as default?

That’s a preference thing, perhaps it makes sense to have this as default but it’s been like this for so long already I don’t know if I wish to break the behavior foe those who prefer not to jump on single.

[ibhagwan]

@hb0nes, 7cede18 sets this option to default, it also renames it from jump_to_single_result to jump1 so it's easier to control from the cmdline.

It's also possible to control the action that happens when a single result is found using jump1_action (used to be named jump_to_single_result_action):

:lua FzfLua.lsp_definitions({jump1=true,jump1_action=FzfLua.actions.file_tabedit})