Fzf-lua keymaps: Detail column hard to see fully

[1ngemar]

Hi,

When searching for your keymaps - 'fzflua keymaps' is great. But the detail column easily gets cut off.
(I haven't got any 'wrap' options to work (?))

Is is feasible to add an option 'show_description = true/false' - or wrap the line?

Or an even better solution?

[ibhagwan]

Regarding wrap and screen real estate, this just came up: #1565

Is is feasible to add an option 'show_description = true/false' - or wrap the line?
Or an even better solution?

I’ll think of something.

[ibhagwan]

I realize it might be the opposite of what you're asking, just FYI, since #1452 it's already possible to turn off the details column with :FzfLua keymaps show_details=false.

I can add show_desc if that's what you're after.

EDIT:
show_desc option added with 95f1d1d:

Can also be conigured via setup under keymaps.show_desc

:FzfLua keymaps show_desc=false

[1ngemar]

Yes; it's the complete details in this case I'm looking for.

Thanks.
/i

[1ngemar]

And is it possible to have a command - to go to the file/line where the keymapping is set/defined? I'm thinking of your (own) custom key mappings, like eg:

[ibhagwan]

And is it possible to have a command - to go to the file/line where the keymapping is set/defined? I'm thinking of your (own) custom key mappings, like eg:

This already happens for lua style key maps using a functions.

[1ngemar]

Ok, I was thinking of a way to jump directly from the fzf-lua keymaps view directly to the definition of the keymapping. So this is possible?

(But although; just a nice-to-have function)

[ibhagwan]

Ok, I was thinking of a way to jump directly from the fzf-lua keymaps view directly to the definition of the keymapping. So this is possible?

(But although; just a nice-to-have function)

As I mentioned, if the keymap is a lua function you can go to defeintion with ctrl-s|v|t (split, vsplit, tab).

Unforuntaely if the mapping is a string it's not possible as the :verbose map <key> doesn't nclude the source, for example:

[1ngemar]

Aha.

Got it, thanks.

[ibhagwan]

@1ngemar, with 95f1d1d you can now use:

:FzfLua keymaps show_desc=false

Can also be conigured via setup under keymaps.show_desc.

[1ngemar]

Yes, thanks. Already tried it. Works great. Den sön 15 dec. 2024 kl 05:49 skrev ibhagwan ***@***.***>:

…

@1ngemar <https://github.com/1ngemar>, with 95f1d1d <95f1d1d> you can now use: :FzfLua keymaps show_desc=false Can also be conigured via setup under keymaps.show_desc. — Reply to this email directly, view it on GitHub <#1566 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ3VYX6ISUG6CLJEWFRKE7T2FUC6FAVCNFSM6AAAAABTTJSK2OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJWHE4TGNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[1ngemar]

Then, regarding our earlier conversation around matching words in grep; fzf, rg. Maybe this is an idea: Make all chars lowercase, eg in hello or Hello or hEllo makes 'hello' Then fabricate a string like so (for all chars a..z) : '[Hh][Ee][Ll][Ll][Oo]' Then, the fzf window will sort (out) the possible multiple regex matches, say if you only search for 'hello'; it will still only show that matched line for 'hello'. But if you use --smart-case and there are multiple matches in the preview window; they will all be highlighted. Maybe that would be a way forward? But I see that the regex line would look messy :) /i Den sön 15 dec. 2024 kl 08:44 skrev Ingemar Åström ***@***.***

…

: Yes, thanks. Already tried it. Works great. Den sön 15 dec. 2024 kl 05:49 skrev ibhagwan ***@***.***>: > @1ngemar <https://github.com/1ngemar>, with 95f1d1d > <95f1d1d> > you can now use: > > :FzfLua keymaps show_desc=false > > Can also be conigured via setup under keymaps.show_desc. > > — > Reply to this email directly, view it on GitHub > <#1566 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BJ3VYX6ISUG6CLJEWFRKE7T2FUC6FAVCNFSM6AAAAABTTJSK2OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJWHE4TGNY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[ibhagwan]

Maybe that would be a way forward? But I see that the regex line would look
messy :)

Messy, prone to error and perhaps also not the prefernace of some users, say you're not using smart case? then you'd also get matches that don't wish to see, that means we also have to adapt the regex to the rg options, IMHO this feels like overly complex for a minor inconvinience so I don't plan on embarking in this anytime soon.

[1ngemar]

Yes. All good. /i Den sön 15 dec. 2024 10:25ibhagwan ***@***.***> skrev:

…

Maybe that would be a way forward? But I see that the regex line would look messy :) Messy, prone to error and perhaps also not the prefernace of some users, say you're not using smart case? then you'd also get matches that don't wish to see, that means we also have to adapt the regex to the rg options, IMHO this feels like overly complex for a minor inconvinience so I don't plan on embarking in this anytime soon. — Reply to this email directly, view it on GitHub <#1566 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ3VYX4BQUN7UN5QKDHGMYD2FVDIXAVCNFSM6AAAAABTTJSK2OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJXGA4DQOI> . You are receiving this because you were mentioned.Message ID: ***@***.***>