• Announcement
• Installation
  • Prerequisites
    • Fonts
  • OS-specific setup
    • fzf
    • macOS
    • Linux
  • Set up Zgenom and the starter kit
• Contents of the kit
  • Included plugins
• Customizing the kit
  • Behavior toggles
    • zqs
      • zqs check-for-updates
      • zqs disable-bindkey-handling
      • zqs disable-1password-agent
      • zqs enable-1password-agent
      • zqs enable-bindkey-handling
      • zqs disable-diff-so-fancy
      • zqs enable-diff-so-fancy
      • zqs disable-omz-plugins
      • zqs enable-control-c-decorator
      • zqs disable-control-c-decorator
      • zqs enable-omz-plugins
      • zqs enable-ssh-askpass-require
      • zqs disable-ssh-askpass-require
      • zqs-disable-ssh-key-listing
      • zqs-enable-ssh-key-listing
      • zqs-disable-ssh-key-loading
      • zqs-enable-ssh-key-loading
      • zqs-disable-zmv-autoloading
      • zqs-enable-zmv-autoloading
      • `zqs-disable-zsh-profiling
      • `zqs-enable-zsh-profiling
      • zqs selfupdate
      • zqs update
      • zqs update-plugins
      • zqs cleanup
      • zqs get-setting
      • zqs set-setting
      • zqs delete-setting
  • Functions and Aliases
    • Customizing with ~/.zshrc.d
  • I like a plugin, but some of the aliases and functions it installs overwrite other commands or aliases I use
  • ZSH options
    • Fragment file directories
  • Self-update Settings
  • Customizing the plugin list
    • Using fragment files
    • Complete plugin list replacement
  • Disabling zmv
  • Disabling oh-my-zsh
• FAQ
  • How do I reconfigure the prompt?
  • Powerlevel 10k warns that there is console output during startup
  • I added a new completion plugin, and it isn't working
  • I get a git error when I try to update the kit
  • GNU stow is warning that stowing zsh would cause conflicts
  • _arguments:comparguments:325: can only be called from completion function
  • Could not open a connection to your authentication agent
  • I want to pin a plugin version
• Other Resources
  • ZSH
  • Dotfiles in general
  • Vim
• Thanks

I've switched the quickstart kit to use zgenom instead of zgen. This should be a painless update since zgenom is a superset of zgen.

This quickstart includes the powerlevel10k ZSH theme, which requires a Powerline-compatible font in your terminal to display status glyphs. Powerline-compatible fonts include many useful glyphs, including the nice branch icon that the theme in this .zshrc uses.

Here are a few good Powerline-compatible fonts:

• Awesome Terminal Fonts - A family of fonts that include some nice monospaced Icons.
• Cascadia Code - Microsoft's Cascadia Code
• Fantasque Awesome Font - A nice monospaced font, patched with Font-Awesome, Octoicons, and Powerline-Glyphs.
• Fira Mono - Mozilla's Fira type family.
• Hack - Another Powerline-compatible font designed for source code and terminal usage.
• Input Mono - A family of fonts designed specifically for code. It offers both monospaced and proportional fonts and includes Powerline glyphs.
• Iosevka - Iosevka is an open source slender monospace sans-serif and slab-serif typeface inspired by Pragmata Pro, M+ and PF DIN Mono, designed to be the ideal font for programming.
• Monoid - Monoid is customizable and optimized for coding with bitmap-like sharpness at 15px line-height even on low res displays.
• Mononoki - Mononoki is a typeface by Matthias Tellen, created to enhance code formatting.
• More Nerd Fonts - Another site to download nerd fonts.
• Nerd fonts - A collection of over 20 patched fonts (over 1,700 variations) & the fontforge font patcher python script for Powerline, devicons, and vim-devicons: includes Droid Sans, Meslo, AnonymousPro, ProFont, Inconsolta, and many more. These can be installed with brew - do brew tap homebrew/cask-fonts && brew install --cask fontname
• Powerline patched font collection - A collection of a dozen or so fonts patched to include Powerline glyphs.
• Victor Mono - Victor Mono is a free programming font with semi-connected cursive italics, symbol ligatures (!=, ->>, =>, ===, <=, >=, ++) and Latin, Cyrillic and Greek characters.
• spacemono - Google's new original monospace display typeface family.

To enable the enhanced history search, you'll need to install fzf. Manual install instructions can be found at fzf and os-specific instructions below.

Now that your fonts and default shell have been set up, install zgenom and the dotfiles from this starter kit repository.

1. Install Zgenom
   1. cd ~
   2. git clone https://github.com/jandamm/zgenom.git
2. Install the starter kit
   1. cd ~
   2. git clone https://github.com/unixorn/zsh-quickstart-kit.git
3. Configure zsh by symlinking the .zshrc, .zsh-functions, .zgen-setup and .zsh_aliases from this repository into your ~.
   1. You can do this with stow by:
      1. cd zsh-quickstart-kit
      2. stow --target=~ zsh. If you have issues using ~ as a target, do stow --target="$HOME" zsh. If you still have errors, symlink the files in the kit's zsh directory into your home directory.

The .zshrc, .zsh_aliases & .zsh_functions files included in this kit enable the plugins listed below.

The zsh-quickstart-kit configures your ZSH environment so that it includes:

• Automatic periodic updates of both zgenom and your plugins
• Cross-session shared history so commands typed in one terminal window can be seen and searched in all your other zsh sessions on the same machine.
• Automatic deduplication of your command history.
• Many more tab completions, courtesy of the zsh-users/zsh-completions repository, and periodic updating to the tip of master of that repository, so you get updates to the extra tab completions.
• Supercharged command history search with fzf.
• Syntax highlighting at the command line.
• Tab completion of Rakefile targets.
• Enabling oh-my-zsh-compatible plugins and themes (via the zgenom framework).
• Various helper functions for interacting with macOS' clipboard, audio volume, Spotlight, and Quicklook. For your convenience, these will only load if you are on a macOS machine so that you can use the same plugin list on any *NIX system.
• If you've installed iTerm2's shell integration, it will automatically be loaded during shell startup.

• chrissicool/zsh-256color - Sets your terminal to 256 colors if available.
• djui/alias-tips - Warns you when you have an alias for the command you just typed and tells you what it is.
• eventi/noreallyjustfuckingstopalready- Deals with Apple's squirrelly DNS resolver. Only loads when you're running on macOS.
• peterhurford/git-it-on.zsh - Opens your current repository on GitHub, in your current branch.
• robSis/zsh-completion-generator - Adds a tool to generate ZSH completion functions for programs missing them by parsing their --help output. Note that this doesn't happen dynamically; you'll have to explicitly run it to create a completion for each command missing one.
• sharat87/pip-app - A set of shell functions to make it easy to install small apps and utilities distributed with pip.
• skx/sysadmin-util - A collection of scripts useful for sysadmins.
• srijanshetty/docker-zsh - Adds completions for docker.
• stackexchange/blackbox - Tom Limoncelli's tool for storing secret information in a repository with GnuPG encryption, automatically decrypting as needed.
• supercrabtree/k - k is a directory lister that also shows git status on files & directories.
• unixorn/1password-op.plugin.zsh - Tab completions for 1Password's op command line tool. Only installs itself if op is in your $PATH.
• unixorn/autoupdate-zgenom - Adds autoupdate (for both zgenom itself, and your plugins) to zgenom.
• unixorn/bitbucket-git-helpers - Adds git helper scripts for bitbucket.
• unixorn/fzf-zsh-plugin - This enables fzf-powered history search.
• unixorn/git-extra-commands - A collection of extra helper scripts for git.
• unixorn/jpb.zshplugin - Some of my standard aliases & functions.
• unixorn/rake-completion.zshplugin - Reads the Rakefile in the current directory so you can tab-complete the Rakefile targets.
• unixorn/tumult.plugin.zsh - Adds macOS-specific functions and scripts. This plugin only adds itself to your $PATH if you're running macOS to allow you to use the same plugin list on macOS and other systems.
• zdharma-continuum/fast-syntax-highlighting - Syntax highlighting as you type.
• zsh-autosuggestions - Adds fish-like autosuggestions to your ZSH sessions.
• zsh-users/zsh-completions - Tab completions for many more applications than come standard with ZSH.
• zsh-users/zsh-history-substring-search - Better history search.

The quickstart kit also uses zgenom to load oh-my-zsh and these plugins:

• aws
• brew - only loaded on macOS
• chruby
• colored-man
• git
• github
• osx - only loaded on macOS
• pip
• python
• rsync
• screen
• sudo
• vagrant

Running the following commands will toggle behavior the next time you start a shell session:

• Prompt selectors - We now use the powerlevel10k prompt. I won't change the prompt out from under people without a way for them to get the old behavior, so there are commands to switch back and forth.
  • zsh-quickstart-select-powerlevel10k - Switch to the powerlevel10k prompt now used as the kit's default.
  • zsh-quickstart-select-bullet-train - Switch back to the bullet-train prompt originally used in the kit.
• You can disable printing the list of ssh keys by executing zqs disable-ssh-key-listing.
• bash prints ^C when you're typing a command and hit control-c to cancel it, so it is easy to see it wasn't executed. By default, ZSH doesn't print the ^C. I prefer seeing the ^C, so by default, the quickstart traps SIGINT and prints the ^C. You can disable this behavior by running zqs disable-control-c-decorator and enable it with zqs enable-control-c-decorator.

As of 2021-11-13, I've added a zqs command to start exposing some of the configurable parts in a more user-friendly way. The zqs command has the following subcommands:

Updates the quickstart kit if it has been longer than seven days since the last update.

Disable bindkey setup and alias expansion in the quickstart .zshrc so people can use plugins like globalias to handle it instead.

Disable using 1Password's ssh agent

Enable using 1Password's ssh agent starting with the next new ZSH session. This is the default behavior when op is in your $PATH.

Let the quickstart's .zshrc configure bindkey setup and alias expansion. This is the default behavior.

Stop loading the diff-so-fancy plugin starting with the next ZSH session.

Start loading the diff-so-fancy plugin starting with the next ZSH session. This is the default behavior.

Set the quickstart to not include any oh-my-zsh plugins from the standard plugin list. Loading omz plugins can make terminal startup significantly slower.

Set the quickstart to create a TRAPINT handler in future zsh sessions to also display control-C when you type control-c. This is the default behavior.

Set the quickstart to not create the TRAPINT handler to display control-C when you type control-c in future zsh sessions.

Sets the quickstart to include the oh-my-zsh plugins from the standard plugin list.

Enable the quickstart to prompt for your ssh passphrase on the command line.

The quickstart will prompt for your ssh passphrase via a gui program. Default behavior.

Don't print the loaded ssh keys when creating a new session.

Print the loaded ssh keys when creating a new session. This is the default behavior.

Don't load ssh keys when creating a new session. Useful if you're storing your private keys in a yubikey.

Load missing ssh private keys when creating a new session. This is the default behavior.

Don't run autoload -U zmv when creating a new session.

Run autoload -U zmv when creating a new session. This is the default behavior.

Disable ZSH's profiler. This is the default.

Turn on ZSH's profiler

Force an immediate update of the quickstart kit.

Update the quickstart kit and all your plugins.

Updates all your plugins.

Cleanup unused plugins after removing them from the list

zqs get-setting NAME [OPTIONAL default value] prints the value of a zqs setting, or if unset and a default value was passed, the specified default.

zqs set-setting NAME VALUE writes a setting.

zqs delete-setting NAME deletes a setting from zqs's crude parameter store.

The .zshrc included in this kit will automatically source any files it finds in ~/.zshrc.d. This happens after plugins are loaded. If you need to set variables or aliases before plugins are loaded, create files in ~/.zshrc.pre-plugins.d.

This makes it easy for you to add extra functions and aliases without having to maintain a separate fork of this repository and allows you to configure the behavior of some of the plugins by setting environment variables.

The files will be sourced in alphanumeric order after loading all the plugins, and I suggest you use a naming scheme of 001-onething, 002-something-else etc., to ensure they're loaded in the order you expect.

Make a file in ~/.zshrc.d named something like 999-reset-aliases. Because files in ~/.zshrc.d are loaded after all the ZSH plugins, you can add lines like unalias xyzzy to remove an alias named xyzzy, or unset -f abcd to remove a function named abcd.

Once you've cleared all the unwanted aliases and functions, you can add new ones with your preferred names.

The quickstart kit does an opinionated (i.e., my way) setup of ZSH options and adds some functions and aliases I like on my systems. I don't want you to have to maintain a separate fork if you don't like them and/or want to add your own, so the kit allows you to override or add behavior by creating fragment files that it will load during session startup.

You can customize the quickstart by adding files to its various zshrc.d directories.

If you want to set variables before the quickstart starts loading plugins to alter their behavior, stick your fragment files in ~/.zshrc.pre-plugins.d.

After the quickstart sets up its aliases, functions, plugins and ZSH options, it will source every fragment file in ~/.zshrc.d.

To make it easier to have macOS, FreeBSD or Linux-specific settings tweaks, the quickstart also supports OS-specific pre & post .zshrc.d directories. If you want a file to only be sourced on a single OS, the quickstart also checks for .zshrc.pre-plugins.$(uname).d and ~/.zshrc.$(uname).d during loading.

The quickstart kit will automatically check for updates every seven days. If you want to change the interval, set QUICKSTART_KIT_REFRESH_IN_DAYS in a file in ~/.zshrc.d. If you're going to disable self-updating entirely, add unset QUICKSTART_KIT_REFRESH_IN_DAYS in a file in ~/.zshrc.d.

I've included what I think is a good starter set of ZSH plugins in this repository. However, everyone has their preferences for their environment.

To make things easier to customize without users having to maintain their own forks, the kit provides two ways to customize the list of plugins it will load.

You can either add a fragment file to ~/.zshrc.add-plugins.d, or you can make a ~/.zsh-quickstart-local-plugin file.

If all you want to do is add plugins to the standard list and you want to still automatically get any new changes I make to that standard list (new plugins, new locations when existing plugins are moved, etc) then adding a file into ~/.zshrc.add-plugins.d with your extra plugins listed as zgenom load githubuser/pluginrepo (one line per plugin) is the way to go. The kit will load its plugins, then add yours on the end. You can add separate files with plugins in the ~/.zshrc.add-plugins.d directory - my personal use case is having one file with all the plugins I use everywhere, and one that has extra plugins I only need on my work machines. This is the easiest option.

If you don't care about future changes to the kit's plugins and want to fully replace the built-in list, then create a ~/.zsh-quickstart-local-plugins file. When the kit detects a file named ~/.zsh-quickstart-local-plugins, its .zshrc will source that instead of running the load-starter-plugin-list function defined in ~/.zgen-setup.

Using ~/.zsh-quickstart-local-plugins is not additive. It will completely replace the kit-provided list of plugins. If you want to just add more plugins, use the fragment file method above.

Creating a .zsh-quickstart-local-plugins from scratch is a pain, so to make customizing your plugin list easier, I've included a .zsh-quickstart-local-plugins-example file at the root of the repository that installs the same plugin list that the kit does by default that you can use as a starting point for your own .zsh-quickstart-local-plugins file.

Copy that to your $HOME/.zsh-quickstart-local-plugins, change the list, and the next time you start a terminal session, you'll get your plugin list loaded instead of the kit's defaults.

The quickstart automatically autoloads zmv. If you want to disable that so you can configure it with another plugin or on your own, run zqs disable-zmv-autoloading.

If you don't want zgenom to load the oh-my-zsh defaults, run zqs-disable-omz-plugins.

You may want to reconfigure your prompt after using it. The quickstart uses the powerlevel10k theme, so you can reconfigure your prompt by running p10k configure.

You see a warning during session startup -

[WARNING]: Console output during zsh initialization detected.
When using Powerlevel10k with instant prompt, console output during zsh
initialization may indicate issues.

You can stifle this output by adding typeset -g POWERLEVEL9K_INSTANT_PROMPT=quiet in a fragment file in ~/.zshrc.pre-plugins.d.

I've had reports that sometimes you may need to reset your completions after adding a new plugin.

rm ~/.zcompdump*
compinit

You try to update the kit, and you get an error similar to this:

From https://github.com/unixorn/zsh-quickstart-kit
0c5bad9..2064c6b master -> origin/master

    755f689...e3f8677 switch-to-zgenom -> origin/switch-to-zgenom (forced update)
    Updating 0c5bad9..2064c6b
    error: Your local changes to the following files would be overwritten by merge:
    zsh/.zshrc
    Please commit your changes or stash them before you merge.
    Aborting

This happens when you edit a file provided by the quickstart kit, in this case, .zshrc. This is annoying, and to let you customize your ZSH settings without being forced to maintain your own fork of the kit, the kit-provided .zshrc will load any files it finds in the various ~/.zshrc.d directories. See Fragment File Directories for more details.

You ran stow --target=/Users/YourUsername zsh in the top level of the repo and stow printed the following error:

WARNING! stowing zsh would cause conflicts:
  * existing target is neither a link nor a directory: .zshrc
All operations aborted.

Per @jefheaton, this is caused when trying to replace an existing .zshrc file. He fixed it by closing ~ in Finder so Finder wouldn't create a .DS_Store file, deleting the existing .DS_Store and removing the old .zshrc. You may have to rename it first if ZSH is keeping the file open, then delete it after closing all your Terminal/iTerm 2 windows.

This has been solved by running zgen update or switching to zgenom. New users of the kit should already be running zgenom. Thanks @RonanJackson, for reporting the fix.

Confirm that ssh-agent is running. If not, Rob Montero has a good blog post on setting up ssh-agent on macOS, and here are instructions for starting ssh-agent with systemd on Linux.

The plugin standard doesn't include a standard way of determining a version. If you need to pin a version of a plugin, the easiest way to do it is to fork the plugin's repository and then have your ~/.zsh-quickstart-local-plugins refer to that.

If you don't want to maintain a fork, you can also have zgenom load from a local directory. So clone the repository, then add something like

zgenom load ~/path/to/your/copy/of/example.plugin.zsh

Then you can tag working versions, pull from upstream for testing, and if the upstream doesn't work for you, check out your last-working-version tag, and zgenom will use your tagged version instead of the tip of the default branch.

• For a list of other ZSH plugins, completions, and themes you might like to use, check out my awesome-zsh-plugins list. It also contains a list of other ZSH tutorials and starter kits.
• Justin Garrison has a good repository that details Mastering ZSH.

dotfiles.github.io/ has a lot of great resources for dotfiles - frameworks for managing them, configurations for editors, and other bootstraps with initial configurations to start from.

If you're using vim, spf13 is an excellent starter configuration and plugin collection.

Many thanks to all the contributors over the years who've helped make the quickstart better.

Made with contributors-img.