I believe in having as few bash functions, aliases, etc. as possible. Others do not agree, so they won't find this useful. At one point my system was configured with the Hashrocket dotmatrix repo, but I've since whittled it away until there's nothing left. There were too many functions and aliases in that config, and the git prompt function is particularly slow compared to the builtin
__git_ps1 variable now available.
The directory layout of this repo is inspired by Zach Holman's excellent dotfiles repo, even though I don't use any of his actual config. You can read about why having a good set of dotfiles is important on Zach's blog.
bash/ is a my bash config scripts:
.bash_profileis usually loaded first for most interactive shells.
.bashrcis initially loaded, and loads other config files.
.bashrc.aliasis a set of aliases that I care about.
.bashrc.localis for local system config, and is omitted.
.bashrc.promptexists purely to set up the bash prompt.
.bashrc.completionis loaded last and sets up all bash completion features and some RVM features.
emacs-live now for my base emacs config: https://github.com/overtone/emacs-live
emacs/ is my emacs-live config file:
It should be symlinked into position:
ln -s ~/dev/dotfiles/emacs/mathiasx-pack ~/.livepacks/
The important file in
git/ is the
.gitconfig file which prepares some of my git aliases and sets my git user.
.gitconfig with your information:
[user] name = Matt Gauger email = firstname.lastname@example.org
The installed Git version should be 1.8.0 or newer to take advantage of some settings and bash prompt settings.
On Linux, you may see errors because bash can't find
__git_ps1 -- especially if you compiled git from scratch. To fix this, I included the
git-prompt.sh script from the git repo in
git/. Move it somewhere like
~/bin and add a line to source it in
Use rylnd's pair script: rylnd/dotfiles
Follow those instructions to install. My own personal fork of the pair script is no longer maintained.
Contains a .tmux.conf file that sets up tmux. Very basic config at this point. Hoping to improve that once I read Brian Hogan's new book.
Use Chris Johnsen's tmux-MacOSX-pasteboard to get paste support in tmux. Follow the instructions to compile it and place it in
.tmux.conf file will call
reattach-to-user-session every time it launches.
vim/ you'll find files to set up vim, naturally:
.vimrcis the main vim config file. I am using Vundle, so all of the vim bundles that I depend on are listed in the 'Vundle' section in
.vimrc. (I previously was using Pathogen, but I've switched to Vundle.)
.vimrc.localis for local vim config and is omitted.
- After symlinking the vim files into place, you must:
- Clone the vundle repo into place:
git clone https://github.com/gmarik/vundle.git ~/.vim/bundle/vundle
- Install the bundles with
:BundleInstallin vim after symlinking things into place.
I don't suggest you go using these files without understanding what they do. But if you must, the files get symlinked into position in your home directory from this directory. Their filenames should remain the same. I highly suggest that if you're going to use pieces of this, that you fork this repo into your own Github account, at the very least. Then remove what you don't want.
I can't guarantee this will work for you. These are my own config files and highly personalized. As noted below in the license, there is no warranty.
Copyright (c) 2012 Matt Gauger
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.