[BUG] Full-path search and globbing leads to `fd` not exit on pipeline closing about fd HOT 5 OPEN

Well, the deeper issue is that fd -p -g '*' doesn't print anything. That's why it never quits, it never even writes anything to the pipe.

from fd.

Oh wait, I guess that's on purpose. * is only matching a single path component. It works with **. See #404 (comment) and 47974b6

from fd.

> (fd -gp '**' / | exit)
# exits normally
> (fd -gp '**' / | fzf)
# exits normally
> fd -gp '**' / | fzf
# exits normally
> (fd -gp '/home/me/**' / | exit)
# exits normally
> (fd -gp '/home/me/**' / | fzf)
# blocks
> fd -gp '/home/me/**' / | fzf
# blocks
> (fd -gpHL '/home/me/**' / | exit)
# forks??
> (fd -gpHL '/home/me/**' / | fzf)
# also forks
> fd -gpHL '/home/me/**' / | fzf
# blocks

from fd.

Hmm I'm not sure what you mean by "forks". But as far as I can tell the behaviour of all those commands is within the expected range. fd will only exit on a closed pipe if it actually tries to write while the pipeline is closed. For something like

> (fd -gp '/home/me/**' / | fzf)

it's quite possible that fd prints all the matching paths while fzf is still running, meaning the pipe is open. When you quit fzf, fd might still be searching the rest of /, but it will never print anything again so it will never learn that the pipe is closed.

See #472 for some related discussion about detecting closed pipes.

from fd.

Thank you, I now undestand the problem. I didn't know how terminating the pipe works, my assumption was that a signal is sent when the receiving process exits, not when the sending process tries to write data.

By "forks" I mean fd starts to consume a lot of CPU and the process becomes independent of where I launched it from. I can even close the terminal and it's still running, as can be inspected in a process monitor utility.

from fd.