Help creating custom fuzzy seach command script.

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I’m sure there’s a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

Trajan@monero.town · 3 months ago

Help creating custom fuzzy seach command script.

/home/addison · 3 months ago

It looks like you haven’t passed a package name to nix-search, so it’s just printing the usage info, and fzf is ingesting the lines of that usage info for you to fuzzy search over.

fzf won’t pass the search query back to whatever program piped in the input. The search query is only used to narrow the results.

I’m not sure how to go about interactively searching nixpkgs with fzf, but you could start by writing a function that accepts a package name or whatever you want to search for and passes it to nix-search. Then fzf can narrow down the results for you.