-
-
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
Fuzzy completion example from wiki is not working #1119
Comments
I'm having the same issue. I use brew to install fzf and I do follow each instruction of the The |
I'm having the same issue only Im using ZSH w/ various terminal emulators |
I had the same problem by installing with a package manager. Then I solved the problem by explicitly sourcing the completion shell file in my shell-rc file. |
My issue was package manager installation. If you run |
It appears that installing fzf via brew cause an issue where the functionality that uses the completion trigger don't work. The solution is to explicitly source those completion files. junegunn/fzf#1119 (comment)
Fuzzy completion like
I was able to solve my auto-completion issue by manually downloading this source file completion.bash and adding it as described. I added the following lines to my
|
I ran into this issue because I was using FZF in combination with iTerm2 and Oh-My-Zsh. I had placed the |
I'm trying to define custom shell completion using example from wiki, and it doesn't work from me. I've put the definition of
_fzf_complete_doge
andcomplete -F _fzf_complete_doge -o default -o bashdefault doge
in a script and sourced it. But when I trydoge <TAB>
(ordoge **<TAB>
) I get default bash path completion. This is GNU bash, version 4.3.48(1)-release.The text was updated successfully, but these errors were encountered: