Runs on Linux and OSX. Configurations for ZSH, SublimeText 3, Java, Ruby, Terminals and others.
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 (Ruby, git, system libraries, and so on), so I structured the project accordingly.
If you're interested in the philosophy behind why projects like these are awesome, you might want to read my post on the subject.
Run this:
bash -c "$(wget -O - https://raw.githubusercontent.com/caarlos0/dotfiles/master/script/install)"This will symlink the appropriate files in .dotfiles to your home directory.
Everything is configured and tweaked within ~/.dotfiles.
dot is a simple script that installs some dependencies, sets sane OS X
defaults, and so on. Tweak this script, and occasionally run dot from
time to time to keep your environment fresh and up-to-date. You can find
this script in bin/.
Everything's built around topic areas. If you're adding a new area to your
forked dotfiles — say, "Erlang" — you can simply add a erlang 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's a few special files in the hierarchy.
- bin/: Anything in
bin/will get added to your$PATHand be made available everywhere. - 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$PATHor similar. - topic/completion.zsh: Any file named
completion.zshis loaded last and is expected to setup autocomplete. - topic/*.symlink: Any files ending in
*.symlinkget 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 runscript/bootstrap. - topic/install.sh: Any file with this name and with exec permission, will ran at bootstrap phase.
- pure prompt (which is awesome!);
- fish-like syntax highlight;
- more completions;
- fish-like substring history search;
- alias-tips to remember you that you have an alias for that;
- zsh-pg a set of utilities to deal with PostgreSQL;
- zsh-git-sync to keep your repositories synced;
- zsh-open-pr to open pull requests from the command line;
- jvm to manage java versions (a la rvm, but simpler);
- mkc to
mkdirandcdin one line. browser.
All those are managed by Antibody, a faster version of Antigen written in Go.
I try to keep it working in both Linux (no specific distro) and OS X, mostly because I use OS X at home and Linux at work.
Yes you can! Pull the repo and run:
$ docker build -t dotfiles .
$ docker run -it dotfilesIt will start a fresh container with my dotfiles inside and dumb git credentials.
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!
- All SC2039 ignores should be fixed (#65);
Feel free to contribute. Pull requests will be automatically checked/linted with Shellcheck.
I forked Holmans' excellent dotfiles and tweaked it to fit my taste. I have also copied one thing or another from other people, so, thanks everyone!