Header action shortcuts not visible enough

[guillenotfound]

So I've tried doing a few searches here to see if I can find a way to get access to the header (mappings):

The problem is that at least for me they will trim so it's not very useful and I could not find a way to show the full header... With telescope you can hit one of these two and it will show you all the possible combinations:

To split vertically, horizontally, ctrl+g,.... I think it would be nice because I feel like I'm missing some mappings so I find my self reading on reddit to see how people are using the plugin lol

I've been using this for a week and I'm impressed, such a piece of art @ibhagwan ! Congrats for making such an amazing tool ;)

[ibhagwan]

To split vertically, horizontally, ctrl+g,.... I think it would be nice because I feel like I'm missing some mappings so I find my self reading on reddit to see how people are using the plugin lol

You can press F1 to see help for all the mappings (customizable):

If you run :FzfLua profiles and select telescope, you can toggle help with ctrl-/ like telescope.

Also play with the F4/F5/F6 to hide / rotate the preview, it should help in this case.

I've been using this for a week and I'm impressed, such a piece of art @ibhagwan ! Congrats for making such an amazing tool ;)

Ty for the kind words friend :)

[ibhagwan]

Ohh exactly what I was looking for, thank you so much!

Something else I'm missing is cycling, like when getting to the end of the list of results and hitting ctrl+n I'd like it to go to the first result, same but the oposite when using ctrl+p. Is there also a setting for that?

fzf_opts .--cycle=true

[guillenotfound]

Ohh I see it has been answered multiple times, my bad for not looking into it with more detail: #861 #1564 (at least)

Would it make sense to have this in the FAQ? https://github.com/ibhagwan/fzf-lua/wiki

I'm going to go check it in detail but so far I have the setup I'm used to, thanks a lot again! <3

[ibhagwan]

Ohh I see it has been answered multiple times, my bad for not looking into it with more detail: #861 #1564 (at least)

Would it make sense to have this in the FAQ? https://github.com/ibhagwan/fzf-lua/wiki

I'm going to go check it in detail but so far I have the setup I'm used to, thanks a lot again! <3

No worries, I answer on the go sometimes so the min answer works too,

Feel free to edit the Wiki, it’s open edit :)

[guillenotfound]

Done, thanks again!

[ibhagwan]

Done, thanks again!

Ty @guillenotfound!

[minusfive]

@ibhagwan suggestion: instead of making interactive headers the default, what about making a single, simple static <F1> for help header? I feel like the interactive header isn't really useful as is since it's typically truncated after the first keymap, and the related code is therefore perhaps doing a bit too much without providing much value.

Happy to take a stab at a PR if you think this is a good idea? For reference this is what I have set up for mine:

Note I'm using 3 keymaps because I'm experimenting to find the most natural for me. I use a corne keyboard due to RSI and my fn keys are on the 3rd layer 'cause I rarely use them, so the default F1 is a bit cumbersome for me.

Here's my code if anyone is interested:

function(_, opts)
  local fzf_utils = require("fzf-lua.utils")
  local fzf_highlights = require("fzf-lua.config").defaults.__HLS

  LazyVim.merge(opts, {
    winopts = {
      -- border = "none",
      height = 0.5,
      width = 1,
      row = 1,
      col = 0,
    },
    keymap = {
      builtin = {
        true,
        ["<C-h>"] = "toggle-help",
        ["<C-/>"] = "toggle-help",
      },
    },
    defaults = {
      RIPGREP_CONFIG_PATH = vim.env.RIPGREP_CONFIG_PATH,
      header = string.format(
        "%s%s%s%s%s%s%s\n\n",
        fzf_utils.ansi_from_hl(fzf_highlights.header_bind, "<C-h>"),
        fzf_utils.ansi_from_hl(fzf_highlights.header_text, ", "),
        fzf_utils.ansi_from_hl(fzf_highlights.header_bind, "<C-/>"),
        fzf_utils.ansi_from_hl(fzf_highlights.header_text, " or "),
        fzf_utils.ansi_from_hl(fzf_highlights.header_bind, "<F1>"),
        fzf_utils.ansi_from_hl(fzf_highlights.header_text, " for "),
        fzf_utils.ansi_from_hl(fzf_highlights.header_bind, "help")
      ),
    },
    grep = {
      rg_glob = true,
    },
  })
end

[ibhagwan]

@ibhagwan suggestion: instead of making interactive headers the default, what about making a single, simple static for help header? I feel like the interactive header isn't really useful as is since it's typically truncated after the fist keymap, and the related code is therefore perhaps doing a bit too much without providing much value.
Happy to take a stab at a PR if you think this is a good idea? For reference this is what I have set up for mine:

I agree with there’s room for improvement but my idea also be to toggle the header inside fzf with a transform bind which fzf added recently, it’s much more flexible and we can show the headers inside fzf instead of relying on the help screen, obviously this all has to be customizable as every user has their own preference.

Perhaps I’ll tackle this sometime soon but unsure yet, if you wanna experiment with a PR go ahead but it would have to be customizable, scalable and not opinionated.