How do I filter out passwords from fish shell history with Sponge?

Use regex patterns in the sponge_regex_patterns variable to match sensitive strings, but be cautious as regex might not cover all cases and requires careful crafting to avoid false positives.

Sponge vs built-in fish history management?

Sponge adds automated filtering based on exit codes and regex, while fish's native history is passive; Sponge is better for proactive cleanup, but lacks retroactive action.

Can I use Sponge with oh-my-fish?

Yes, since it's a standard fish plugin installed via Fisher, it should integrate seamlessly with oh-my-fish or other fish framework setups.

How to undo a filtered command in Sponge?

Adjust the sponge_delay variable to keep entries longer or use session-only settings, but once purged, commands are permanently removed from history.

Does Sponge work with fish history search shortcuts like Ctrl+R?

Yes, by filtering out unwanted entries, it makes history search results cleaner and more relevant, improving productivity when recalling commands.

Open-Awesome

Categories Alternatives Stacks Self-Hosted Explore

Open-Awesome

Terms Privacy About GitHub RSS

Sponge — Fish Shell Command History Cleaner | Open Awesome

Home
Sponge

Sponge

MITShell1.1.0

A fish shell plugin that automatically cleans your command history by filtering out typos, failed commands, and unwanted entries.

GitHub

433 stars4 forks0 contributors

What is Sponge?

Sponge is a fish shell plugin that automatically cleans your command history by filtering out typos, failed commands, and unwanted entries. It runs in the background to ensure your history remains relevant and clutter-free, solving the problem of searching through outdated or incorrect commands.

Target Audience

Fish shell users who want a cleaner command history, particularly developers and power users who frequently use the terminal and value productivity and privacy.

Value Proposition

Developers choose Sponge for its seamless automation and customization; it works out-of-the-box to filter common issues like typos, while offering advanced features like regex filtering and custom functions for tailored control over history management.

Overview

🧽 Clean fish history from typos automatically

Use Cases

Best For

Automatically removing failed commands from fish shell history
Filtering out typos and misspelled commands to keep history clean

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

Excluding sensitive data (e.g., IP addresses) from shell history using regex

Customizing history filtering with user-defined logic and exit code rules

Improving command search efficiency by reducing clutter in fish shell

Managing shell history privacy by automatically purging unwanted entries

Not Ideal For

Users of shells other than fish (e.g., bash or zsh) needing history cleanup
Developers requiring automatic retroactive filtering of pre-existing history without manual intervention
Environments where shell prompt responsiveness is critical, due to synchronous filter execution