Is there a way to run "resume" but fallback to "builtin" if there's nothing to resume?

[heygarrett]

I'd love to set a keymap that either resumes the most recent picker or opens the builtin picker. I suppose then I'd also need a keymap to switch from any picker to the builtin picker. 🤔

[heygarrett]

Thinking more about this, if I'd need a second keymap anyway I might as well just have a separate keymap to "resume". 😅

[heygarrett]

Well now I'm curious. 😁 Is it possible to currently configure, or would it require code changes in the plugin?

[ibhagwan]

Well now I'm curious. 😁 Is it possible to currently configure, or would it require code changes in the plugin?

Actually, this would require some clarification, when you say “nothing to resume” does that mean no query? Because after the first run there is always something to resume as each picker maintains their own resume.

[heygarrett]

I currently have a keymap that runs this function:

function()
	require("fzf_lua.cmd").run_command()
end

If I replace that with this:

function()
	require("fzf_lua").resume()
end

Then I get this when I use it:

[Fzf-lua] No resume data available.

[ibhagwan]

I currently have a keymap that runs this function:

function()
	require("fzf_lua.cmd").run_command()
end

If I replace that with this:

function()
	require("fzf_lua").resume()
end

Then I get this when I use it:

[Fzf-lua] No resume data available.

local resume = function()
  local fzf = require("fzf-lua")
  if fzf.config.__resume_data or not fzf.config.__resume_data.opts then
    fzf.builtin()
  end
  fzf.resume()
end
``‘

[heygarrett]

Thanks! TIL about require("fzf-lua").builtin(). 😅 The only other part I'd need is a keymap to "go back" to the builtin picker from any other picker. Have a suggestion for how to configure that? Would it go directly in the top-level actions table?

[nyngwang]

Possibly related: #1900,

where I try to create a toggle keymap under hide profile(might differ from your case) to either unhide the most recent fzf-lua window (built-in pickers), or, open a new picker specified by my keymap.

[ibhagwan]

It was actually my discovery today of profiles, and the hide profile in particular, that prompted me to start experimenting with integrating "resume" into my workflow, and resulted in this discussion. 😁

Once “hide” is fully mature I think it should be the default, I think we’re getting there :)

Unless @phanen thinks differently.

[nyngwang]

Once “hide” is fully mature I think it should be the default

@ibhagwan Does it cover the case where we can have more than one hidden pickers? My current experience on hide profile is great if I use one fzf-lua picker at a time:
files-->files-->files--(no need to use files)-->tabs-->tabs-->tabs--(no need to use tabs)-->...
but not the case if I "interleave" different pickers in the procedure (unhide can't help restoring states):
files--(hidden files state lost)-->tabs--(hidden tabs state lost)-->files-->...

I also wish that hide profile can be the default since I don't like re-positioning my selection there are so many entries in the list.

[ibhagwan]

Once “hide” is fully mature I think it should be the default

@ibhagwan Does it cover the case where we can have more than one hidden pickers? My current experience on hide profile is great if I use one fzf-lua picker at a time: files-->files-->files-->tabs-->tabs-->tabs but not the case if I "interleave" different pickers in the procedure (unhide can't help restoring states): files-->tabs--(hidden files state lost)-->files--(hidden tabs state lost)-->...

I also wish that hide profile can be the default since I don't like re-positioning my selection there are so many entries in the list.

Nope, that would need a refactor of the entire code base to allow for multiple hidden fzf processes (it’s currently singleton fzf).

[nyngwang]

That's fine. I like hide profile but I also don't want fzf-lua to be very complex for this good-to-have feature :D I just need to be more careful when I execute another pickers. (also the "many entries" case rarely got interleaved in my usecase, I mentioned it just because sometimes I wrongly hit my keybind, lol)

[ibhagwan]

That's fine. I like hide profile but I also don't want fzf-lua to be very complex for this good-to-have feature :D I just need to be more careful when I execute another pickers. (also the "many entries" case rarely got interleaved in my usecase, I mentioned it just because sometimes I wrongly hit my keybind, lol)

One day when fzf --listen (upstream) enables all the functionality we need I might get motivated to change the architecture altogether and make this possible.