alacritty: a blazingly fast terminal, written in rust.karabiner elements: a powerful utility for keyboard customization on macOS.lazygit: simple terminal UI for git commands.neofetch: a command line system information tool.neovim: a vim-fork focused on extensibility and usability.sketchybar: a highly customisable macOS status bar replacement.skhd: simple hotkey daemon for macOS.tmux: a terminal multiplexer.yabai: a tiling window manager for macOS based on binary space partitioning.zsh.
Everything is installed with homebrew, the missing package manager for macOS (or Linux).
- Create an install script
- Test the install script
- In what order are zsh startup files sourced?
This is explained in detail in zsh docs:
Commands are first read from /etc/zshenv; this cannot be overridden. [...] Commands are then read from $ZDOTDIR/.zshenv. If the shell is a login shell, commands are read from /etc/zprofile and then $ZDOTDIR/.zprofile. Then, if the shell is interactive, commands are read from /etc/zshrc and then $ZDOTDIR/.zshrc. Finally, if the shell is a login shell, /etc/zlogin and $ZDOTDIR/.zlogin are read.
In other words, this is the order in which these files get read. Keep in mind that it reads first from the system-wide file (i.e. /etc/zshenv) then from the file in your home directory (~/.zshenv):
.zshenv → .zprofile → .zshrc → .zlogin → .zlogout