ffipf VS fzf.el

Thanks :) Judging by the upvotes there is some interest in the module like this, so I'll keep working on it. It'll take some time before it's usable by others, I think I should be able to clean up the code and write a better Elisp wrapper in a week or two. I used Ivy for displaying candidates because it was by far the easiest integration: literally 1 line of code (https://github.com/piotrklibert/ffipf/blob/master/elisp/ffip.el#L41), but I'm more used to Helm, so integration with it will definitely come next. I don't use Selectrum/Prescient/Embark/etc. personally, but I don't think writing integration with them would be hard. The main selling point of this module is that it's synchronous yet still fast enough, so there's no need for implementing async behavior when integrating it with a framework.

Another alternative is fzf.el [1] which properly wraps fzf.

[1] https://github.com/bling/fzf.el

I have a similar flow. FYI bling's fzf wrapper provides fzf-with-command to work around this limitation

E.g.: https://github.com/bling/fzf.el

I have tried `find-name-dired`, `find-dired`, `find-grep-dired`, https://github.com/bling/fzf.el `fzf-directory` function, etc., but can find the functionality. I tried searching for some variable change in emacs but could not find one. Thanks for your help.

I think this exists for ivy (counsel-file-jump) and you can also do it via ido ; I think most of the time you don’t want to search in all sub dirs because it can take a long time to search through. For situations where performance can be an issue you can use fzf again via ivy / counsel or https://github.com/bling/fzf.el

True. I checked and there are such packages already: https://github.com/bling/fzf.el