jldeen does dotfiles - forked from holman's repo
Run the following to configure macOS from scratch...
bash -c "$(curl -fsSL https://raw.githubusercontent.com/jldeen/dotfiles/mac/configure.sh)"
Run the following to configure WSL from scratch...
bash -c "$(curl -fsSL https://raw.githubusercontent.com/jldeen/dotfiles/wsl/configure.sh)"
There are two "master" branches here: WSL and MacOS; there are two "dev" branches here wsl-dev and mac-dev.
Run this if you wish to run from clone:
git clone https://github.com/jldeen/dotfiles.git ~/.dotfiles cd ~/.dotfiles script/bootstrap
This will symlink the appropriate files in
.dotfiles to your home directory.
Everything is configured and tweaked within
The main file you'll want to change right off the bat is
which sets up a few paths that'll be different on your particular machine. You also might want to configure
.tmux.conf since I run a few scripts in the status bar.
dot is a simple script that installs some dependencies, sets sane macOS
defaults, and so on. Tweak this script, and occasionally run
time to time to keep your environment fresh and up-to-date. You can find
this script in
Your dotfiles are how you personalize your system. These are mine.
I was a little tired of having long alias files and everything strewn about (which is extremely common on other dotfiles projects, too). That led to this project being much more topic-centric. I realized I could split a lot of things up into the main areas I used (git, system libraries, and so on), so I structured the project accordingly. I also created branches for WSL and MacOS since those are my two environments.
If you're interested in the philosophy behind why projects like these are awesome, you might want to read Holman's post on the subject.
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
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 holman's or Fork mine, remove what you don't use, and build on what you do use.
There's a few special files in the hierarchy.
- bin/: Anything in
bin/will get added to your
$PATHand be made available everywhere.
- Brewfile: This is a list of applications for Homebrew Cask to install: things like Chrome and 1Password and Adium and stuff. Might want to edit this file before running any initial setup.
- topic/*.zsh: Any files ending in
.zshget loaded into your environment.
- topic/path.zsh: Any file named
path.zshis loaded first and is expected to setup
- topic/completion.zsh: Any file named
completion.zshis loaded last and is expected to setup autocomplete.
- topic/install.sh: Any file named
install.shis executed when you run
script/install. To avoid being loaded automatically, its extension is
- topic/*.symlink: Any file ending in
*.symlinkgets 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
I want this to work for everyone; that means when you clone it down it should
work for you even though you may not have
rbenv installed, for example. That
said, I do use this as my dotfiles, so there's a good chance I may break
something if I forget to make a check for a dependency.
If you're brand-new to the project and run into any blockers, please open an issue on this repository and I'd love to get it fixed for you!
Holman forked Ryan Bates' excellent dotfiles for a couple years before the weight of his changes and tweaks inspired him to finally roll his own. But Ryan's dotfiles were an easy way to get into bash customization, and then to jump ship to zsh a bit later. A decent amount of the code in these dotfiles stem or are inspired from Ryan's original project.