junegunn/fzf

This is useful on non-customized machines, but I always install fzf now, including the shell integrations like fuzzy history search bound to ctrl-r. https://github.com/junegunn/fzf

I tried atuin and then switched back to fzf[0]. It's less features but that's not necessarily a negative. [0] https://github.com/junegunn/fzf

Sweet! Well-expressed, and well-explored. It's easy to setup an interface that makes search a bit easier still, including showing you a list as you interactively filter history, with fzf, [gh-fzf]. Examples of what users use most frequently, the key-bindings.{bash,zsh} has history key binds [arch-fzf]. The developer, junegunn, writes about it more generally, and all the other fun ways you can apply it [dev-fzf]. For a few years, I wrote history files per shell-spawn, and loaded a batch of history from recent days to keep fresh what's in the immediately searchable history. Nowadays, I've just offloaded that to atuin [atuin], which I install from brew or with cargo binstall. Much less confi…

1. https://github.com/junegunn/fzf for fuzzy search. Great for easily searching and selecting git branches + tags + commits, commands from shell history, files, shell jobs, processes, etc. 2. https://github.com/casey/just for more structured scripting.

…lacement - [oxide]( https://github.com/ajeetdsouza/zoxide ) smart and fast cd replacement -[atuin]( https://atuin.sh/ ) ctrl + r and shell history finder - [fzf]( https://github.com/junegunn/fzf ) fuzzy finder ``` # Plugin Manager declare -A ZINIT ZINIT[NO_ALIASES]=1 ZINIT_HOME="${XDG_DATA_HOME:-${HOME}/.local/share}/zinit/zinit.git" [ ! -d $ZINIT_HOME ] && mkdir -p "$(dirname $ZINIT_HOME)" [ ! -d $ZINIT_HOME/.git ] && git clone https://github.com/zdharma-continuum/zinit.git "$ZINIT_HOME" source "${ZINIT_HOME}/zinit.zsh" autoload -Uz compinit; compinit # Plugins zinit light Aloxaf/fzf-tab zstyle ':fzf-tab:' use-fzf-default-opts yes zinit light zdharma-continuum/fast-syntax-highlightin…

That sounds like you've already got it pretty well figured out, then. :) If you did want to get fuzzy-matching in your workflow, I might recommend using building a small alias/function with fzf[1], rather than using zoxide. Something like `dst=$(cat ~/myprojectlist.txt | fzf) && cd $dst && source sourceme`. You wouldn't get the list sorted by most-frequent/recent like you do with zoxide, but it sounds like that's not what you're looking for anyways. [1] https://github.com/junegunn/fzf