An Intro to zsh-utils
ZSH is an extremely powerful tool which can be very useful but hard to configure. zsh-utils aims to fix this. It’s a small configuration framework which aims to provide a base to work off of without getting in your way if you want to dive deeper later.
Why Use a Config Framework?
If you’ve ever started zsh without a config file before, you’ve probably seen the following mass of text before:
Even after using ZSH for multiple years, if I see this, it’s very rare that I take the time to go through this process every time: it’s daunting and almost every time you’ll end up with a config file that’s different on each of your computers, leading to tons of frustration.
That’s where I see the main advantages of a config framework: providing a much better out of the box ZSH experience and providing a base to build a personal config off of.
What Is This?
Taken from the project README, zsh-utils is “a minimal set of ZSH plugins designed to be low-friction and low-complexity.”
After getting frustrated with the maintenance of prezto and oh-my-zsh, I decided to write my own small config framework, in a similar vein to some of the starter kits.
Why Another Framework?
There were a number of main problems I noticed during my time maintaining prezto:
- Most ZSH config frameworks contain a bundled plugin manager along with a number of modules. It would make more sense to officially support an external plugin manager and focus development on the plugins.
- It takes a ton of work to get a module ready for prezto, even if it’s small.
- A number of large frameworks set up very strange defaults.
- Many plugins end up being nothing more than a small wrapper around an external repo. Most of this work could be handled by plugin managers.
- Some plugin managers build very non-standard ways to configure ZSH (prezto puts a ton of config values in zstyle and oh-my-zsh has their own custom theme format).
- They just do too much. All I’m really looking for is a small wrapper around the built-in ZSH features.
- So many modules have way too many options, often because they’re trying to do too many things.
That being said, there are a number of strengths to large configuration frameworks as well.
- Plugins can work well together. As an example, prezto’s git plugin provides a git-info command which can be used by prompts to display git information without the prompts having to implement this themselves.
- Having a number of plugins bundled together in one place makes it simple to enable the ones you want without having to do a bunch of additional work.
These are not really something I’m looking for. I want to use a shell as a shell and keep everything as simple as possible so it doesn’t get overwhelming.
Ok, So Why This One?
This project aims to solve some of the problems faced by larger frameworks by focusing on the following clear goals:
- Loadable by any compatible plugin manager
- Plugins will be kept small, relatively inflexible, well documented, and well organized
- No external dependencies without very good reason
- Focus on improving the existing experience rather than expanding it
Each plugin has a very focused purpose:
completionconfigures and loads basic tab completion (imagine bash tab completion on steroids). It’s also recommended to use an additional set of zsh-completions because this plugin only sets up the completion system and doesn’t provide completions for common utils.
editorsets up some keybinds to fix some rough edges. It adds a few missing default key-binds such as Home/End and aims to add a few Vim features to the vi keybind set.
historyconfigures and loads the shell history systems.
promptruns initializes the built-in zsh theming system and provides a place for maintainers to put the prompt they use.
utilitymakes it easier to switch between operating systems by adding aliases for common operations so you don’t need to remember different commands across platforms.
That’s it! There are no plugins for programming languages. There are no custom formats. And there is no configuration outside loading the plugins and optionally overriding ZSH settings.
Sounds Great! How Do I Start?
If this is something that sounds useful to you, it’s fairly easy to get started.
Simply replace your
.zshrc with the following snippet. This is copied directly from the setup in the zsh-utils README.
It downloads antigen, a simple plugin manager, straight from the source if it doesn’t exist and loads all the zsh-utils plugins along with a few other very commonly used external plugins.
[[ ! -d "$HOME/.antigen" ]] && git clone https://github.com/zsh-users/antigen.git "$HOME/.antigen" source "$HOME/.antigen/antigen.zsh" # Set the default plugin repo to be zsh-utils antigen use belak/zsh-utils # Specify completions we want before the completion module antigen bundle zsh-users/zsh-completions # Specify plugins we want antigen bundle editor antigen bundle history antigen bundle prompt antigen bundle utility antigen bundle completion # Specify additional external plugins we want antigen bundle zsh-users/zsh-syntax-highlighting # Load everything antigen apply # Set any settings or overrides here prompt belak bindkey -e
Alternatively, my dotfiles are a good resource and starting point.
Just use ZSH! If you have any problems, feel free to file an issue or open a pull request if you’re feeling up for it.
Want to talk more about this? There are discussion threads at the following places:
Thanks for reading!
#dotfiles #zsh #zsh-utils