-
Notifications
You must be signed in to change notification settings - Fork 6
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
Single tab triggers completion rather than double tab #22
Comments
Hello, It is not really by 'design' but more due to the way how bash completion works. Even without this, i always found weird to have to hit twice Since i don't have a tweak for this now, you could change the key used to select a result in fzf. This way, hitting as an example, use
|
I don't see why is it weird to hit twice to display results. But I understand that it might be difficult to implement technically if bash completion doesn't provide enough flexibility. I will think about changing fzf's default key binding, although I'm quite used to it so the option doesn't sound very attractive :) |
Perhaps this is by design, in which case would be nice to hear the motivation behind that. It is mentioned in the README that the hotkey is .
When not using fzf-obc, one is used to complete the currently typed text, while a shows the whole list of available completions. With fzf-obc, habitually typing
ls /<TAB><TAB>
results in the completion list showing due to the first , and then the first item in the list being selected due to the second one. Of course a user can re-train their behavior if necessary, but I wonder if that is useful, perhaps it would be better to keep the traditional way?The text was updated successfully, but these errors were encountered: