[Feature request] fzf integration

[DRSDavidSoft]

^{Originally posted by @mattdkerr March 11, 2024 From: #2927}

Suggestion

fzf clink integration in cmder shell

Extra info/examples/attachments

https://github.com/chrisant996/clink-fzf
or
https://github.com/chrisant996/clink-gizmos

---

@chrisant996 Can you please give a short list of requirements for implementing this in Cmder, if any? How much additional space would you estimate this will require?

Originally posted by @DRSDavidSoft in #2927

[DRSDavidSoft]

@chrisant996 I would appreciate it if you could please re-post the original fzf integration comments you posted on the original issue (#2927) here, for future reference

I attempted to split the auto self update discussions, which have been moved to https://github.com/orgs/cmderdev/discussions/3066, but now this new issue lacks the context of the previous fzf integration issue.

[chrisant996]

Originally posted by @chrisant996 in #2927 on 2024/05/31; re-posted here for tracking purposes on 2026/02/16

It's covered in detail in the docs here: https://github.com/chrisant996/clink-fzf/#fzf-integration-for-clink

Note the settings and key bindings.

Here is a quick summary to get you started:

@chrisant996 Can you please give a short list of requirements for implementing this in Cmder, if any?

These things are needed:

1. Cmder would need to include fzf.exe (available from fzf).
2. Cmder would need to include fzf.lua (available from clink-fzf).
3. But before Cmder can include fzf.lua, I will have to make some changes to the fzf.lua script. Otherwise when Cmder includes the script it will interfere with everyone who is already using clink-fzf or clink-gizmos, and it will cause errors (it wasn't designed to have multiple copies of it all loaded at the same time, and if Cmder includes it then that will start happening for all Cmder users who were already using clink-fzf).

How much additional space would you estimate this will require?

The size of fzf.exe, which is around 4 MB.

I also found this interesting gist for using fzf for history:
https://gist.github.com/rupeshtr78/ed42a23aec87b8463e4f04bec0308d63

No, don't use that:

Clink-fzf already has support for fzf history. The cited gist is missing all of the rest of the fzf support. The gist appears to be only trying to change clink-fzf's history implementation to print "Searching History" first, but it has bugs in how it tries to do that, and it won't work properly. (And the official fzf support in other shells doesn't print that.)