Is there any way to remap enter in fzf?

[nguyenvukhang]

Is there any way to do something like this?

{
  'ibhagwan/fzf-lua',
  opts = {
    keymap = {
      fzf = {
        ['enter'] = 'select-all+accept',
        ['ctrl-a'] = 'select-all+accept',
      },
    },
  },
}

My end goal is to make it such that when I press enter on a search result, it will do the default action on the selected entry, and then send all the other entries to the quickfix list. I can already achieve this with ctrl-a (in the context of the above mapping) with something like this

actions = {
  ['default'] = function(selected, opts)
    opts.copen = false
    actions.file_sel_to_qf(selected, opts)
    actions.file_edit({ selected[1] }, opts)
  end
},

My question then is, can I achieve what ctrl-a does but with enter? Even when I remap it as above, enter still only seems to perform the accept action, instead of select-all+accept.

[nguyenvukhang]

After a quick dive into the source code, it seems that enter in particular has been reserved for some RPC calls, making it harder than other keys to remap:

{
  "ctrl-a:select-all+accept",
  "alt-Q:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 4 nil {+} {q} {n}",
  "enter:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 5 nil {+} {q} {n}",
  "ctrl-s:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 2 nil {+} {q} {n}",
  "ctrl-t:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 1 nil {+} {q} {n}",
  "ctrl-v:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 7 nil {+} {q} {n}",
  "alt-q:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 6 nil {+} {q} {n}",
  "esc:execute-silent:'/usr/local/bin/nvim' -u NONE -l '/home/khang/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/rpc.lua' 3 nil {+} {q} {n}"
} 

[nguyenvukhang]

FWIW, this hack accomplishes what I aimed to do, closing because it seems that at the moment there is no properly exposed API to do this.

diff --git a/lua/fzf-lua/core.lua b/lua/fzf-lua/core.lua
index 0ebfa23..9e2dedd 100644
--- a/lua/fzf-lua/core.lua
+++ b/lua/fzf-lua/core.lua
@@ -595,6 +595,9 @@ M.create_fzf_binds = function(opts)
       action = action:gsub("accept%s-$", "print(enter)+accept")
     end
     local bind = string.format("%s:%s", key, action)
+    if key == "enter" then
+      bind = string.format("%s:select-all+%s", key, action)
+    end
     -- Separate "transform|execute|execute-silent" binds to their own `--bind` argument, this
     -- way we can use `transform:...` and not be forced to use brackets, i.e. `transform(...)`
     -- this enables us to use brackets in the inner actions, e.g. "zero:transform:rebind(...)"

[ibhagwan]

You don’t need the hack, define enter in the actions map and add a prefix to it:

actions = {
  ["enter"] = { fn = FzfLua.actions.file_edit, prefix = "select-all" }
}

In your case:

actions = {
  ['enter'] = {
    fn = function(selected, opts)
      opts.copen = false
      actions.file_sel_to_qf(selected, opts)
      actions.file_edit({ selected[1] }, opts)
    end,
    prefix = "select-all",
  }
},

[ibhagwan]

After a quick dive into the source code, it seems that enter in particular has been reserved for some RPC calls, making it harder than other keys to remap:

Enter isn’t “reserved”, it’s mapped as the default action which you can reconfigure (as I posted above), the RPC calls you’re seeing are the “hide” profile callbacks so that you can resume the process from where you left so that enter won’t terminate the fzf process.

If you configure a different profile that doesn’t contain the “hide” profile (default is border-fused+hide) you’ll see a different configuration without the execute-silent callbacks, instead you’ll see …accept(enter).

[nguyenvukhang]

Thanks for the help! This works out perfectly for my use case.