0.53.0: --bind behaviour changed? about fzf HOT 4 CLOSED

it's quite a breaking change

Yeah, but I'd say it was a misuse of a feature, like the spacebar heating case.

from fzf.

Yes, it is intentional. execute action is for executing an external program in the alternate screen without leaving fzf, and it isn't supposed to affect the final output of fzf.

For example, when you run selected=$(ls | fzf --bind 'ctrl-o:execute:vim {}'), you don't want any output from Vim in the final output of fzf. Also, prior to 0.53.0, you would have to redirect the standard output of Vim to /dev/tty for it to work properly in this case. Considering the original purpose of execute, this was confusing and not ergonomic.

Another mistake here is using execute where you should be using execute-silent. execute runs the command in the alternate screen, you'll notice screen flashing.

fzf --bind 'space:execute-silent(ls)+accept' --height 30%

how can I now replicate the prior-0.53.0 behaviour?

1. Use print action

fzf --bind 'f1:print(f1)+accept' fzf --bind 'f2:print(f2)+abort'

2. Use become action

fzf --bind 'f1:become:echo f1; echo {}' --bind 'f2:become:echo f2; exit 1'

3. Use --expect

If you just need the key names to be printed, --expect is the simplest.

fzf --expect f1,f2

from fzf.

So, for the reference, it's

--bind 'f2:print(ccc)+accept'

instead of

--bind='f2:execute(printf ccc)+accept'

to get ccc aaa from the example above. And (with optional exit 1 if needed)

--bind 'f1:become:echo bbb' 

instead of

--bind='f1:execute(printf bbb)+abort'

to get bbb.

While certainly looking more logical and more consistent, it's quite a breaking change, I'd say...

from fzf.

Forgot to say thanks for the explanation :)

from fzf.