Skip to content

marklabrecque-ab/dotfiles

 
 

Repository files navigation

joelpittet’s dotfiles

Mathias Bynens’ dotfiles with Cottsers' tweaks and some personal tweaks.

Notable features

Drush

This repository includes Drush (latest dev version) as a git submodule. To update Drush, cd into your local dotfiles repository and run:

./drushup.sh

Then commit the changes (if any).

Brett Terpstra-esque bash prompt

Includes a slightly tweaked version of the useful and good-looking prompt posted by Brett Terpstra in 2009. Follow the link to learn more about it. In short: full path displayed, current time, average CPU load for the past minute, git branch.

Others

Homebrew formulas

  • z - A fuzzy way to navigate directories on the command line.
  • git-ftp - Deploy to (S)FTP from your local git repositories.

Aliases

Adds a bunch of git and drush aliases. Some of these are muscle memory, some will eventually be removed because I never use them.

Installation

Using Git and the bootstrap script

You can clone the repository wherever you want. (I like to keep it in ~/dotfiles.) The bootstrapper script will pull in the latest version and copy the files to your home folder.

git clone --recursive https://github.com/joelpittet/dotfiles.git && cd dotfiles && source bootstrap.sh

To update, cd into your local dotfiles repository and then:

source bootstrap.sh

Alternatively, to update while avoiding the confirmation prompt:

set -- -f; source bootstrap.sh

Git-free install

To install these dotfiles without Git (you won't get Drush though):

cd; curl -#L https://github.com/joelpittet/dotfiles/tarball/master | tar -xzv --strip-components 1 --exclude={README.md,bootstrap.sh,drushup.sh,.gitmodules}

To update later on, just run that command again.

Specify the $PATH

If ~/.path exists, it will be sourced along with the other files, before any feature testing (such as detecting which version of ls is being used) takes place.

Here’s an example ~/.path file that adds ~/utils to the $PATH:

export PATH="$HOME/utils:$PATH"

Add custom commands without creating a new fork

If ~/.extra exists, it will be sourced along with the other files. You can use this to add a few custom commands without the need to fork this entire repository, or to add commands you don’t want to commit to a public repository.

My ~/.extra looks something like this:

# Git credentials
GIT_AUTHOR_NAME="Joel Pittet"
GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME"
git config --global user.name "$GIT_AUTHOR_NAME"
GIT_AUTHOR_EMAIL="joel@pittet.ca"
GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
git config --global user.email "$GIT_AUTHOR_EMAIL"

You could also use ~/.extra to override settings, functions and aliases from my dotfiles repository. It’s probably better to fork this repository instead, though. Or better yet, fork Mathias’!

Sensible OS X defaults

When setting up a new Mac, you may want to set some sensible OS X defaults:

./.osx

Install Homebrew formulae

When setting up a new Mac, you may want to install some common Homebrew formulae (after installing Homebrew, of course):

./.brew

Feedback

Ping me on Twitter.

Thanks to…

About

Personal system setup (Mac OS X)

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Vim Script 82.4%
  • Shell 17.6%