# Kakoune Fuzzy Find

**URL:** <https://discuss.kakoune.com/t/kakoune-fuzzy-find/2640>\
**Category:** Terminal Tools\
**Created:** [January 28, 2025, 8:28am UTC](https://discuss.kakoune.com/t/kakoune-fuzzy-find/2640 "2025-01-28T08:28:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Screwtapello](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/screwtapello/32/12_2.png) [@Screwtapello](https://discuss.kakoune.com/u/Screwtapello)\
**Post date:** [January 28, 2025, 8:28am UTC](https://discuss.kakoune.com/t/kakoune-fuzzy-find/2640/1 "2025-01-28T08:28:52Z")

</div>

Hanging around the Kakoune community, I occasionally see people asking questions about how to integrate fuzzy-find tools like [fzf](https://github.com/junegunn/fzf) into Kakoune, and it seems to be quite difficult. So I wondered how hard it would be to do it the other way around: build a fuzzy-find tool on top of Kakoune’s `:prompt` command.

> **[Screwtape / kakoune-fuzzy-find · GitLab](https://gitlab.com/Screwtapello/kakoune-fuzzy-find)**
>
> GitLab.com

It turns out, it’s pretty easy! One thing I _did_ learn while writing it, though, is that when you launch a process from a shell script, it inherits the file-descriptors of the shell, _unless_ you’re starting the process in the background, in which case it will have its stdin redirected from `/dev/null`. So if you have a shell-script and need to redirect its’ stdin to somewhere else while you do other things, you need to do a little dance to avoid the shell’s default behaviour.