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
Right now you have to pipe to fzf, and as you type fzf will filter the lines based on the text therein.
After reading this I've thought that it'd be really cool to add a flag to specify a query, which will allow fzf to be used without a pipe.
It might seem initially as an equal, albeit weirder, way to rephrase the usage of fzf (since command | fzf is equal to `fzf --query="command"). But this will allow for the query to change as you type to fzf!
A specifically interesting use-case:
fzf --query="git log -S{}" --preview="git show ..."
As you type, you will see the result of a git pickaxe search (looking for a commit containing a certain word [in the diff]), while the preview shows the hunk containing the change.
I believe adding that option would allow even for the development of tools with awesome interactivity.
What do you think?
edit: rephrasing
The text was updated successfully, but these errors were encountered:
Right now you have to pipe to fzf, and as you type fzf will filter the lines based on the text therein.
After reading this I've thought that it'd be really cool to add a flag to specify a query, which will allow fzf to be used without a pipe.
It might seem initially as an equal, albeit weirder, way to rephrase the usage of fzf (since
command | fzf
is equal to `fzf --query="command"). But this will allow for the query to change as you type to fzf!A specifically interesting use-case:
fzf --query="git log -S{}" --preview="git show ..."
As you type, you will see the result of a git pickaxe search (looking for a commit containing a certain word [in the diff]), while the preview shows the hunk containing the change.
I believe adding that option would allow even for the development of tools with awesome interactivity.
What do you think?
edit: rephrasing
The text was updated successfully, but these errors were encountered: