-
Notifications
You must be signed in to change notification settings - Fork 10
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
fzftselect supports tag completion #18
Comments
Hey! Tab completion is an interesting use case. Tab selecting a precise result is somewhat tangential of a selection/filtering mechanism to fzf. I think in this case I would recommend you lean into fzf's search syntax. Specifically, because of its powerful filtering, you can actually start with a more basic query, i.e., all your tags, and then filter using the syntax. A helpful command you could check out is |
not quite the same thing. my tag file is pretty big, several GBs. fzf whereas with tab completion, I can start type then press not so much with fzf |
Gotcha, you want to use fast builtin tab completion for tags instead of loading the entire tags file and fzf filtering. Regarding builtin tab completion — does pressing the tab key autocomplete an entire tag entry, or just as many characters until the next character has multiple matches? At what point would you want to pipe the results to fzf? |
the first tab shows me a grid view and vim command line is not changed. the rest tabs iterate through the matching list and vim command line is changed to the current tag. other chars are reflected as is on the command line, and can be triggered for further tabs. as far as I can tell, there is no auto fill up to the next branching point, although I wish it does.
|
That makes sense and sounds like a performant pipeline. I don't have the bandwidth, but it's a good feature request 👍 |
hi, I noticed fzftselect doesn't have tab completion as the builtin tselect has. so if I type in a partial tag name then press tab, vim's tselect gives me all tags matching the prefix so far without selecting/committing any of them, just like bash tab completion, whereas with fzftselect, I just get a
^I
symbol (the literal tab char?) on the command line, which is somewhat inconvenient, since I didn't get the completions, and I have to remove the unintended^I
. this prevents fzftselect as a dropin replacement to the builtin tselect. any chance to have fzftselect behaves the same here? thanks.The text was updated successfully, but these errors were encountered: