Leon Klingele wrote:
How to debug this?
Try removing all functionality in fzf that still allows you to reproduce the bug.
'fzf' is producing "some output" which is causing confusion; trying to narrow that down would be the likely way to proceed. Alternatively, you might try running your combination in something that stores all I/O. Googling 'recording a tty session' will bring up several programs that work to record a session. Then you can find the output that is causing the confusion. Then its a matter of determining if it is the correct output and if so, put it in a separate shell script and "echo" it to output as a demo of how the [correct?] output causes bash to misbehave. Either that or you'll see that the output isn't correct for what you are wanting it to do. (I.e. if you were expecting it to goto a new line on linux and it only put out a 'CR', you'd see that the output was incorrect). Make sense?