- I maintain this repo as my dotfiles, but I'm keenly aware people are using it for theirs.
- You're quite welcome to make suggestions, however I may decline if it's not of personal value to me.
- If you're starting off consider forking mathias or alrra. paulmillr and gf3 also have great setups
- fork this to your own acct
- clone that repo
- read and run parts of
setup-a-new-machine.sh - read and run
symlink-setup.sh- git config needs attention, read the notes.
- use it. yay!
- commit/push changes you want.
- you can also hypothetically cherry-pick commits from me and mathias and our fork ecosystem.
.aliases and .functions
So many goodies.
Basically it makes typing into the prompt amazing.
- tab like crazy for autocompletion that doesnt suck. tab all the things. srsly.
- no more that says "Display all 1745 possibilities? (y or n)" YAY
- type
cat <uparrow>to see your previouscats and use them. - case insensitivity.
- tab all the livelong day.
z helps you jump around to whatever folder. It uses actual real magic to determine where you should jump to. Seperately there's some ... aliases to shorten cd ../.. and .., .... etc. Then, if you have a folder open in Finder, cdf will bring you to it.
z dotfiles
z blog
.... # drop back equivalent to cd ../../..
z public
cdf # cd to whatever's up in Finderz learns only once its installed so you'll have to cd around for a bit to get it taught.
Lastly, I use open . to open Finder from this path. (That's just available normally.)
.sift.conf- sift (faster than grep, ack, ag).vimrc,.vim- vim config, obv..inputrc- behavior of the actual prompt line
.aliases.bash_profile.bash_prompt.bashrc.exports.functions.extra- not included, explained above
setup-a-new-machine.sh- random apps i need installedsymlink-setup.sh- sets up symlinks for all dotfiles and vim config..osx- run on a fresh osx setupbrew.sh&brew-cask.sh- homebrew initialization
.git.gitattributes.gitconfig.gitignore
There will be items that don't belong to be committed to a git repo, because either 1) it shoudn't be the same across your machines or 2) it shouldn't be in a git repo. Kick it off like this:
touch ~/.extra && $EDITOR $_
I have some EXPORTS, my PATH construction, and a few aliases for ssh'ing into my servers in there.
I don't know how other folks manage their $PATH, but this is how I do mine:
# The top-most paths override here.
PATH=/opt/local/bin
PATH=$PATH:/opt/local/sbin
PATH=$PATH:/bin
PATH=$PATH:~/.rvm/bin
PATH=$PATH:~/code/git-friendly
# ...
export PATHMathias's repo is the canonical for this, but you should probably run his or mine after reviewing it.
./.osxOne-off binaries that aren't via an npm global or homebrew. git open, wifi-password, coloredlogcat, git-overwritten, and subl for Sublime Text.
If you edit this stuff, install Dotfiles Syntax Highlighting via Package Control