A ZSH plugin that maintains separate shell histories per directory and allows toggling between local and global history with ^G.
Per-Directory-History is a ZSH plugin that maintains separate command histories for each directory while also preserving a global history. It solves the problem of cluttered shell histories by organizing commands contextually, allowing developers to quickly access relevant past commands based on their current working directory.
ZSH users, particularly developers and system administrators who work across multiple projects or directories and want to keep their command histories organized and context-specific.
Developers choose this plugin because it uniquely combines per-directory history with global history and allows instant toggling between them, offering both organization and flexibility without losing any command history data.
Per directory history for zsh, as well as global history, and the ability to toggle between them with ^G.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Maintains separate histories for each directory, keeping project-specific commands easily accessible without global clutter, as highlighted in the README's focus on reducing history noise.
Allows seamless switching between local and global histories using ^G or a customizable shortcut via PER_DIRECTORY_HISTORY_TOGGLE, enhancing workflow flexibility as described in the usage section.
Saves every command to both per-directory and global histories, ensuring history preservation regardless of toggle state, a key feature emphasized in the README's dual saving mechanism.
Works as a standalone script or an Oh-My-Zsh plugin, offering easy adoption in various ZSH environments, as noted in the README's compatibility section.
Exclusively for ZSH, making it incompatible with other shells like Bash or Fish, which limits its utility for users in mixed-shell environments.
Duplicates history by saving commands to both local and global files, potentially increasing disk usage, especially with numerous directories, a trade-off not addressed in the README.
Requires sourcing the script or configuring as a plugin, which can be cumbersome for users unfamiliar with ZSH customization, as the README only provides basic installation steps.