Killing 'fd' during long-running search takes long

[sharkdp]

If there are only very little search results and I press Ctrl-C, fd does not stop. The process only seems to exit when the next search result is found (and new output is generated).

This can be tested with

> fd --follow non-existing-pattern /
# try to kill the process with Ctrl-C

[sharkdp]

This seems to be related to the changes in c0bfc65

@Doxterpepper Do you have any idea how we could exit immediately (instead of waiting for the next output)?

[Doxterpepper]

Yea this is kinda a big bug, if fd searches a large enough directory and only one item is to be found it will never exit via ctrl-c until it finds that one entry. That could be a really long time and may be a pretty common use case. To fix this we need to exit from the sender thread gracefully as well when we handle ctrl-c.

I'm currently looking into this.