It is a common practice to store environment variables in a .env file in development. This file is read by tools such as foreman and dotenv. This file can contain sensitive information such as secret keys and should always be excluded from version control
Newer versions of vim (such as 7.3.923) syntax highlight Rackup and JSON files correctly. In the interest of keeping the dotfiles slim and our machines up-to-date, I think the solution is to remove these from dotfiles and install a newer version of vim in thoughtbot/laptop: thoughtbot/laptop#118
The primary use case for me is to `git push staging` and `git push production` from the master branch using our typical git workflow: https://github.com/thoughtbot/guides/tree/master/protocol#deploy
* Mimics GNU screen's ctrl+a a
This is Mac OS X-specific. Including this line in the dotfiles causes `tmux` and `tmux new -s new-session` to break with `[exited]`. I personally don't do copy-pasteable work inside tmux anymore. I'm sure this is valuable to some of the thoughtbot vim users but I'm thinking it better belongs above `DO NOT EDIT BELOW THIS LINE` as custom configuration for those users.
It's not very useful to be dropped into the middle of your diff when opening a new commit. This change prevents cursor position from being restored for the `gitcommit` filetype.
I've had this in [my own dotfiles] for a while now, and really like having the separation of what I consider to be code/configuration from what to me feels more like a Gemfile, in that it lists out all of the external dependencies in a single place. [my own dotfiles](https://github.com/calebthompson/dotfiles/blob/master/vim/vimrc.bundles.symlink) * Awesomer vundle integration: * Refactor .vimrc and .vimrc.bundles to support standalone BundleInstall. * Install vim bundles as part of install.sh without sourcing the normal vimrc, which prevents error messages from uninstalled plugins referenced in the main vimrc.