-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: support fzf init <shell> initialization #3505
Comments
Hasn’t this been actually accomplished in https://github.com/junegunn/fzf/tree/0.48.0 with And related question: what is the purpose of these files in |
Let me leave a comment for cross reference. I've partially answered to the questions in akinomyoga/ble.sh#441 (reply in thread).
Yes, I guess this issue can be closed now.
For the finer control mentioned in README, cf |
man fzf
)Info
Feature request
Support
fzf init <shell>
initialization (like in starship, zoxide, navi etc) to facilitate fzf integration with other tools (file managers, utilities etc) because this style of initialization doesn't require knowledge about key-bindings and completion file paths (which can vary in different packages), fzf will generate apropriate files by itself. Such an approach also cleans up shell rc files. Instead of:only one line of code is required:
For backward compatibility reasons, the feature implementation can just output existing key-bindings and completion files to stdout.
completion
andkeybindings
parameters can be supported to getcompletion.<shell>
orkey-bindings.<shell>
implementations separately:The text was updated successfully, but these errors were encountered: