A pluggable, fast ZSH setup built from small, opt-in configurations.
Quick start · Configurations · How it loads · The prompt · Writing your own
Shell is a configuration for ZSH and Oh My Zsh, focused on Linux. Instead of one big .zshrc, every tool gets its own small file. You switch on only what you use.
- 🔌 Pluggable. One file per tool or SDK in
zsh/env-available/. Enable one with a symlink, the same way nginx and Apache do withsites-availableandsites-enabled. - 🛡️ Safe by design. Every configuration checks that its tool exists before touching
PATHor defining aliases, so a file is a no-op on a machine without that tool. - ⚡ Fast. An interactive shell starts in about 40 ms (measured with
zsh -i -c exiton the author's laptop), and a script that startszshpays about 4 ms for the environment files. - 📜 Sensible history. 100,000 entries, shared between sessions, with duplicates and blank lines removed.
- 🎨 A custom prompt. The
otypetheme shows user, host, kernel, directory, git status and the version of the project's language. - 🧹 Unique
PATH. De-duplicated once, centrally, withtypeset -U path.
| Needed | Why |
|---|---|
| ZSH | the shell itself |
git and curl |
for the installer |
| Oh My Zsh | zshrc sources it. install.sh expects it to be there, link.sh installs it if missing |
| Vim (optional) | fallback $EDITOR when Emacs is not installed, target of the vi alias |
Fresh machine: clone and link in one step.
$ curl -L https://raw.githubusercontent.com/otype/shell/main/bin/install.sh | bashThe installer clones the repo to ~/.shell (override with SHELL_ROOT, pick a branch or tag with SHELL_GIT_TAG, use USE_SSH=1 to clone over SSH). It refuses to run if that directory already exists.
Existing checkout: link it into $HOME with link.sh.
$ ~/.shell/link.shIt links zshenv, zshrc, zsh and zprofile, installs Oh My Zsh with a plain git clone if it is missing, and moves any existing real file out of the way to <name>.bak-<timestamp>.
Finally, make ZSH your login shell and open a new terminal:
$ chsh -s "$(command -v zsh)"Everything in zsh/env-available/ is off by default. To enable a configuration, link it into env-enabled/ and restart your terminal:
$ cd ~/.zsh/env-enabled && ln -nsf ../env-available/zshenv-dockerTo disable it again, remove the link. Read a file before enabling it, some contain paths that are specific to one machine.
| Config | What it does |
|---|---|
zshenv-android |
ANDROID_HOME and the SDK tools on PATH |
zshenv-asdf |
loads asdf and its completions |
zshenv-awsume |
the awsume alias and its completion |
zshenv-cargo |
Rust: sources ~/.cargo/env |
zshenv-claude |
plugin folder for Claude Code sessions (specific to the author) |
zshenv-docker |
Docker shortcuts (di, dps, dl, …) |
zshenv-elixir |
persistent shell history for IEx |
zshenv-emacs |
$EDITOR and $VISUAL via emacsclient, aliases e, ec, se |
zshenv-flutter |
Flutter on PATH |
zshenv-general |
Emacs key bindings, ^S forward history search, small aliases (h, sl, bc, vi) |
zshenv-git |
gpr, gpt, gprf |
zshenv-goenv |
goenv |
zshenv-gpg |
GPG_TTY set the zsh-safe way |
zshenv-hashicorp |
Packer, Terraform, Vault, … from /opt/hashicorp/bin |
zshenv-lua |
LuaRocks binaries on PATH |
zshenv-nvm |
loads nvm and its completion |
zshenv-omarchy |
loads Omarchy's shell aliases just before the first prompt, after Oh My Zsh |
zshenv-pmd |
PMD completion and PATH |
zshenv-podman |
Podman shortcuts (pi, pps, pl, …) |
zshenv-powerline |
starts powerline-daemon |
zshenv-pyenv |
pyenv |
zshenv-python |
the user-level Python bin directory (~/.local/bin) on PATH |
zshenv-rbenv |
rbenv |
zshenv-sdkman |
SDKMAN! |
zshenv-sshagent |
uses the systemd user ssh-agent.socket for SSH_AUTH_SOCK |
zshenv-tfenv |
tfenv |
zshenv-tilix |
aliases to dump and load the Tilix configuration |
zshenv-virtualenv |
virtualenvwrapper (marked as possibly outdated in the file) |
Note
The links in env-enabled/ are ignored by git (see its .gitignore), so what you enable stays local to each machine.
ZSH reads its startup files in a fixed order. Each one has a single job here:
| Step | File | Read by | What it does |
|---|---|---|---|
| 1 | zshenv |
every shell, scripts included | makes PATH unique, then sources every file in zsh/env-enabled/ |
| 2 | zprofile |
login shells | KEYTIMEOUT, $PAGER, a default LANG, adds ~/bin and ~/.local/bin to PATH |
| 3 | zshrc |
interactive shells | history size and file, completion path, Oh My Zsh (theme and plugins), then zsh/zshoptions |
zshrc enables these Oh My Zsh plugins: colored-man-pages, colorize, emacs, git, git-extras, gh, history and sudo. zsh-autosuggestions and zsh-syntax-highlighting are not installed. Add more to the plugins=(...) line, a list is in the Oh My Zsh plugin wiki.
Because zshenv runs for every shell, it only exports variables and extends PATH. Aliases, key bindings and terminal settings are limited to interactive shells with [[ -o interactive ]] || return 0.
The otype theme is set in zshrc with ZSH_THEME="otype". It prints something like this (illustrative):
(user@host<7.2.15>) :: ~/projects/api on main 👍
|:. (Node:v24.1.0)
- Left:
user@host, the kernel version, the current directory, then the git branch and status (dirty, untracked, ahead, …). - Right: the version of a language, but only when the current directory has its marker file:
mix.exs(Elixir),pubspec.yaml(Flutter),go.mod(Go),pom.xml(Java),package.json(Node),setup.pyorrequirements.txt(Python),Gemfile(Ruby),Cargo.toml(Rust).
The branch symbol needs a Powerline-patched font, and the git status uses emoji.
- Create
zsh/env-available/zshenv-<name>. - Guard everything. Check with
command -v,[[ -d … ]]or(( $+commands[tool] ))first, so the file does nothing when the tool is missing. - Extend
PATHwith the array form,path+=("$dir")orpath=("$dir" $path).export PATH=…bypasses the de-duplication fromzshenv. Do not add per-file de-duplication. - Keep aliases interactive-only. Put
[[ -o interactive ]] || return 0above them. Variables that scripts need (likeEDITOR) go above that line. - Enable it with
ln -nsf ../env-available/zshenv-<name>inzsh/env-enabled/.
There is no build or test tooling. Check a change by opening a new shell, or with zsh -i -c exit (no output means no errors).
MIT © otype