This was forked from holman's excellent base. I added some more vim config and brushed up the tmux configuration.
Run this:
git clone https://github.com/kaihowl/dotfiles.git ~/.dotfiles
cd ~/.dotfiles
# Actual sourcing/linking of dotfiles and installation
script/bootstrap
# Optionally, run the tests
script/test
This will symlink the appropriate files in .dotfiles
to your home directory.
Everything is configured and tweaked within ~/.dotfiles
.
The main file you'll want to change right off the bat is zsh/zshrc.symlink
,
which sets up a few paths that'll be different on your particular machine.
Reasoning: Indiscriminate dependencies and not part of my day-to-day tech stack.
Reasoning: I am impatient and like my pull requests small and focussed. A longer CI runtime is counter-productive.
Everything's built around topic areas. If you're adding a new area to your
forked dotfiles — say, "Java" — you can simply add a java
directory and put
files in there. Anything with an extension of .zsh
will get automatically
included into your shell. Anything with an extension of .symlink
will get
symlinked without extension into $HOME
when you run script/bootstrap
.
A lot of stuff. Seriously, a lot of stuff. Check them out in the file browser above and see what components may mesh up with you. Fork it, remove what you don't use, and build on what you do use.
There are a few special files in the hierarchy.
bin/
will get added to your $PATH
and be made
available everywhere..zsh
get loaded into your
environment.path.zsh
is loaded first and is
expected to set up $PATH
or similar.completion.zsh
is loaded
last and is expected to set up autocomplete.*.symlink
get symlinked into
your $HOME
. This is so you can keep all of those versioned in your dotfiles
but still keep those autoloaded files in your home directory. These get
symlinked in when you run script/bootstrap
.Performance results on master branch.
I forked from holman's dotfiles, and he forked Ryan Bates' excellent dotfiles.