My personal toolkit. Locally I use neovim
for my editor, zsh
for my shell with starship.rs
for the prompt and tmux
for window managment. For my terminal I am currently using wezterm
but I keep configuration for alacritty
and kitty
handy. bashrc
, vimrc
and gitconfig
are standalone and can be copied to remote hosts if I need.
The setup
script will do most of the work but there are a few dependencies that need to be installed manually with the system package manager or built from source. cargo
can be used for the rust dependencies:
zsh
tmux
(greater than 3.2a, prefer head)neovim
(greater than 0.8, prefer nightly)bat
/batcat
rg
/ripgrep
Fonts also need to be configured on the base host (the system that runs the terminal). I haven't automated this because terminal installation is also manual:
if [ uname = "Darwin" ]; then
FONT_DIR="$HOME/Library/Fonts"
else
FONT_DIR="$HOME/.local/share/fonts"
fi
wget https://github.com/ryanoasis/nerd-fonts/releases/download/v3.0.2/Hack.zip
mkdir -p $FONT_DIR
unzip Hack.zip -d $FONT_DIR
git clone git@github.com:kevinhughes27/dotfiles.git ~/dotfiles
cd ~/dotfiles
./setup.sh
neovim
will bootstrap itself on first open. npm
and pip
will be needed for Mason to successfully install language servers.
From a configured system ./setup.sh -r <remote>
can be used to copy my standalone bashrc
, vimrc
and gitconfig
to a remote host. fzf
will also be copied.
My zshrc
will source a ~/.localrc
file if it exists for any system or work specific settings. This lets me maintain one set of dotfiles while still having flexability. It is pretty common for programs to automatically add config to your dotfiles and when that happens I can see the changes in git and move them to localrc.