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
If running e.g. fzf --height=30% --bind=alt-enter:"execute(echo TEST)" and hitting alt-enter, the text TEST is not printed although the command seems to be executed (can be tested with e.g. touch).
It works without the option --height. It also works if stdout is piped to a file directly (fzf [...] >/tmp/testfile), but it does not work if piped through cat (fzf [...] | cat).
The text was updated successfully, but these errors were encountered:
Hi, I spend some time today debugging this and came to the same observation as this issue. @doak did you manage to find a workaround this (besides redirecting fzf's output?)
I think that the reason it works when redirecting to a file vs. to stdout is because in the latter case the output actually gets printed but it immediately gets overwritten by fzf trying to maintain the --height argument.
Does not seems to be an issue on Windows. When switching to light renderer (i.e. height <=99), there is some garbage (maybe some escape code) printed before the text, but that's it.
(recording is 8 fps)
man fzf
)Info
Problem / Steps to reproduce
If running e.g.
fzf --height=30% --bind=alt-enter:"execute(echo TEST)"
and hittingalt-enter
, the textTEST
is not printed although the command seems to be executed (can be tested with e.g.touch
).It works without the option
--height
. It also works if stdout is piped to a file directly (fzf [...] >/tmp/testfile
), but it does not work if piped throughcat
(fzf [...] | cat
).The text was updated successfully, but these errors were encountered: