dotfiles 0,1,1,1 travis-ci

:octocat: dotfiles ❤ Testing my dotfiles repo on OS X to get my work environment ready in just a few moments. #VIM + #ZSH + #TMUX = Best Developer Environment

Overview | Features | Installation | Updating | Setup | Structure | Credits | License

This is a repository with my configuration files, those that in Linux/OS X normally are these files under the $HOME directory that are hidden and preceded by a dot, AKA dotfiles.


The primary goal is to increase CLI productivity on OS X, though many scripts run just fine on any POSIX implementation and it is easy to build environment again by running just the installation command of one-liner.

My primary OS is OS X (10.10.x) and some of these configurations are tuned to work on that platform. The bash files are more generic and friendly toward other Unix-based operating systems.



  • OS X Yosemite (MacBook, Retina 12-inch, Early 2015)
  • (Full-screen)
  • Solarized (base 16)
  • Tmux 1.9a
  • Zsh 5.0.5
  • Vim (7.4 Huge +clipboard +lua)


Note: You can clone or fork them freely, but I don’t guarantee that they fit you.



The easiest way to install this dotfiles is to open up a terminal, type the installation command below: Run the following command to set up a new machine:

Installation command Copy
cURL bash -c "$(curl -fsSL" :clipboard:
Wget bash -c "$(wget -qO -" :clipboard:
  • It is almost the same as the command below except for executing through a Web site directly.

    $ make install

    It is not necessary to perform make install at all if this repository was installed by the installation command.

  • General download method using the git command:

    $ git clone ~/.dotfiles
    $ cd ~/.dotfiles && make install

    Incidentally, make install will perform the following tasks.

    • make update; Updating dotfiles repository
    • make deploy; Deploying dot files
    • make init; Initializing some settings

What’s inside?

  1. Download this repository
  2. Deploy (i.e. copy or create symlink) dot files to your home directory; make deploy
  3. Run all programs for setup in ./etc/init/ directory; make init (Optional: when running the installation command specify -s init as an argument)

When the installation command format is not curl -L URL | sh but sh -c "$(curl -L URL)", shell will be restart automatically. If this is not the case, it is necessary to restart your shell manually.


Quick installation

To quickly install:

$ curl -sL | sh

Difference of Installation and Quick Installation is that the latter one-liner is shorter than the former one (including typing the number of shift key). However, because when you install in the Quick installation shell is not re-boot, it is necessary to perform the exec sh yourself.

42 chars bash -c "$(curl -sL"
30 chars curl -sL | sh

Actually notation of the shell may be sh instead of bash. Regardless of the sh realities, it is possible to do the same installation process because the script file that is used to the installation command is a shell script that conforms to POSIX.

Note: If you want to use the curl, in order to follow the redirect -L flag is essential. On the other hand, it is possible to omit -s flag because it is meant that silent or quiet mode makes curl mute.



To update later on, just run this command.

$ make update

In addition, there are several git submodules included in this configuration. On a new installation these submodules need to be initialized and updated.




All configuration files for setup is stored within the etc/init/ directory. By running the command below, you can interactively setup all preferences.

$ make init

To run make init immediately after running the installation command:

$ bash -c "$(curl -L" -s init

Init scripts

  • Build and install customized Vim (+clipboard, +lua)
  • Globalize your home directory name
  • Install antigen the zsh plugin manager
  • Install pygments the generic syntax highlighter written in python
  • Install Homebrew the missing package manager for OS X
  • Install the CLI tool that comes with Xcode
  • Run ‘brew install’ based on the Brewfile
  • Sensible OS X defaults
  • Setup Karabiner (formerly KeyRemap4MacBook)

For more information about initializing, see also ./etc/


To install the Vim plugins, run this command.

$ vim +NeoBundleInit +qall

Vim plugins are not installed from you just running the installation command. To install the plugins, you must specify the -c 'NeoBundleInit' as an argument when starting Vim. By doing so, install immediately neobundle.vim and other plugins (requires: git in $PATH, Vim 7.2+, a lot of time, Wi-Fi).

To use these plugins effectively, features of Vim needs normal or more.


Make the configuration file for personal use. Copy and paste the following to personal configuration file, e.g. ~/.sh.local

# Git credentials
# Not under version control to prevent people from
# accidentally committing with your details
GIT_AUTHOR_EMAIL="[email protected]"

# Set the credentials (modifies ~/.gitconfig)
git config --global "$GIT_AUTHOR_NAME"
git config --global "$GIT_AUTHOR_EMAIL"


The easiest way to change your shell is to use the chsh command. You can also give chsh the -s option; this will set your shell for you, without requiring you to enter an editor.

$ chsh -s /bin/zsh

Note: The shell that you wish to use must be present in the /etc/shells file.


When setting up a new Mac, you may want to perform the following tasks mainly.

  • Install the Xcode Command Line Tools

    You need to have Xcode or, at the very minimum, the Xcode Command Line Tools, which are available as a much smaller download.

    The easiest way to install the Xcode Command Line Tools in OS X 10.9+ is to open up a terminal, type xcode-select --install and follow the prompts.

  • Install Homebrew and setup their formulae

    Since OS X does not have a native package manager that you can use from the command line, Brew (also known as Homebrew), has filled in.

    After installing Homebrew, you may want to install some common Homebrew formulae:

    $ make init
  • Run some defaults commands

    It can set many hidden settings and preferences in Mac OS X, and in individual applications.

All of these are included in the make init for OS X. For more detail, see also here of documentation of OS X operation.



If you have Vagrant and Virtualbox already installed, this is both faster and cleaner than downloading and compiling all the dependencies in OS X. To install, simply do the following:

$ vagrant init
$ vagrant up

If you want to try my dotfiles without polluting your development environment, it would be best to use a Vagrant. Have fun by setting and please remove it after finish.

$ vagrant destroy -f   # when finished, destroy the VM





Acknowledgment; I established this dotfiles referring to the following user’s repositories. Thus, I would appreciate it if you used my repository for reference. Thanks.




Copyright © 2014 “BABAROT” b4b4r07

Licensed under the MIT license.

Unless attributed otherwise, everything is under the MIT licence. Some stuff is not from me, and without attribution, and I no longer remember where I got it from. I apologize for that.


Related Repositories



:octocat: dotfiles ❤ Testing my dotfiles repo on OS X to get my work environment ready in just a few moments. #VIM + #ZSH + #TMUX = Best Developer Environment ...



dotfiles for vim, git, zsh, weechat, openbox, xterm, and many others. Install with: lndir -silent /path/to/dotfiles $HOME ...



:art: I created a logo for your dotfiles. Well, for @pengwynn's [dotfiles](, but you can use it too. ...



To use: git clone --bare [email protected]:bronson/dotfiles.git .dotfiles.git ; alias .f="git --work-tree='$HOME' --git-dir='$HOME'/.dotfiles.git" ; WARNING .f reset --hard HEAD ...



dotfiles dotfiles!! ...

Top Contributors

b4b4r07 babarot bitdeli-chef keita03301995


-   v0.1 zip tar