You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keybindings are obviously super useful, but they are finite and sometimes hard to remember -- great for power users writing their own fzf scripts, less so for novices using somebody else's fzf-based widget. What about binding to multicharacter sequences as well?
Now I can type > pizza: hawaiian to narrow my search list to only pizzas.
(See my related issue on dynamic query formatting/rewriting for a more fleshed-out example mimicking the omnibar "search engine" functionality of Firefox/Chrome (and probably all browsers nowadays) and Alfred/Albert.)
There are some kinks here to be sure, even from my layman's perspective:
What do you do with the trigger sequence in the query once it's been fired? Leave it? Delete it? Move it into the prompt?
If the trigger stays in the query after it's typed, does it fire on every change? Just once?
What if the trigger is in the middle of another word? (Presumably, easiest thing is to avoid this problem by require the trigger at the beginning of the query separated by whitespace.)
I have no idea what implementation challenges this might bring up, but this seems like it could be pretty cool. Certainly it would make the widget I have in mind super slick.
The text was updated successfully, but these errors were encountered:
man fzf
)Info
Idea
Keybindings are obviously super useful, but they are finite and sometimes hard to remember -- great for power users writing their own
fzf
scripts, less so for novices using somebody else'sfzf
-based widget. What about binding to multicharacter sequences as well?Now I can type
> pizza: hawaiian
to narrow my search list to only pizzas.(See my related issue on dynamic query formatting/rewriting for a more fleshed-out example mimicking the omnibar "search engine" functionality of Firefox/Chrome (and probably all browsers nowadays) and Alfred/Albert.)
There are some kinks here to be sure, even from my layman's perspective:
I have no idea what implementation challenges this might bring up, but this seems like it could be pretty cool. Certainly it would make the widget I have in mind super slick.
The text was updated successfully, but these errors were encountered: