A Zsh plugin that replaces Ctrl+R shell history search with peco's interactive fuzzy filtering interface.
zsh-peco-history is a Zsh plugin that replaces the standard Ctrl+R shell history search with an interactive interface powered by peco. It allows users to visually browse, filter, and select previous commands from their terminal history using fuzzy matching and customizable layouts. The plugin solves the problem of cumbersome history navigation in traditional Zsh by providing a more intuitive and efficient way to access past commands.
Zsh users who frequently work in the terminal and want a better way to search and reuse their command history. This includes developers, system administrators, and power users who value terminal productivity.
Developers choose zsh-peco-history because it significantly improves the history search experience compared to Zsh's default implementation. The key advantage is peco's interactive filtering interface, which makes finding and selecting past commands faster and more visual, especially for users with extensive command histories.
Search shell history with peco when pressing ctrl+r.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Replaces Zsh's default Ctrl+R with peco's visual interface, making command browsing more intuitive, as shown in the screenshot and usage instructions.
Allows fuzzy matching via peco's filtering modes, enabling quick command retrieval, configurable with ZSH_PECO_HISTORY_OPTS like --initial-filter=Fuzzy.
Offers configurable layouts such as bottom-up via ZSH_PECO_HISTORY_OPTS, improving visibility based on user preference.
Seamlessly integrates with popular Zsh plugin managers like Oh My Zsh and Antigen, simplifying installation as detailed in the README.
Requires peco and tools like tac or tail, plus perl/awk/uniq for deduplication, adding setup complexity and potential compatibility issues.
Exclusively works with Zsh, making it unsuitable for users of other shells like Bash or Fish, narrowing its applicability.
Users must manage separate peco configuration (e.g., ~/.peco/config.json) for optimal use, as recommended in the README, which adds extra steps.