2.0 upgrade

[cloud8421]

This is the PR for 2.0 release, with a substantial changelog:

• Hermes now relies on Tmux 1.8, mostly for its ability to pipe on copy: this removes the need for the custom launchd service and simplifies the approach used in the configuration. Other niceties have been added as well, like fullscreen panes toggle and vertical block selection.
• Pathogen removed in favour of Vundle: this makes the whole plugin management for Vim easier.
• Removes Powerline (deprecated anyway) for a custom, extremely lightweight status line based on https://github.com/maciakl/vim-neatstatus
• Hermes ships a set of default Rails projections to use with Rails.vim
• Autocompletion plugins have been removed in favour of a lighter, more focused custom function.
• RVM removed in favour of rbenv. This may be controversial, but having set up at least 7-8 different laptops in the last few months, rbenv has proven to be easier and more reliable.
• Dynamic path setup: this means that Hermes can be installed anywhere in the system.
• Molokai color scheme
• Spellcheck configuration (borrowed from https://github.com/thoughtbot) for good documentation/commit messages editing.
• Better selection of Vim plugins, with more focus on speed and performance.
• Simple Homebrew management thanks to brew bundle.

[leemeichin]

You can configure git-prompt.sh to show this automatically (I presume you're using that), and use PROMPT_COMMAND instead of PS1 for the colours git st uses.

# In addition, if you set GIT_PS1_SHOWDIRTYSTATE to a nonempty value,
# unstaged (*) and staged (+) changes will be shown next to the branch
# name.  You can configure this per-repository with the
# bash.showDirtyState variable, which defaults to true once
# GIT_PS1_SHOWDIRTYSTATE is enabled.

# If you would like a colored hint about the current dirty state, set
# GIT_PS1_SHOWCOLORHINTS to a nonempty value. The colors are based on
# the colored output of "git status -sb" and are available only when
# using __git_ps1 for PROMPT_COMMAND or precmd.

https://raw.github.com/git/git/master/contrib/completion/git-prompt.sh

[cloud8421]

Thanks! It would be much better, I'll investigate this!

[leemeichin]

Seems like you can use a Brewfile now, if all the dependencies are installed via Homebrew: https://coderwall.com/p/afmnbq

Can't see any official documentation yet. Must be pretty new.

[cloud8421]

It does look like it: a search shows this PR: Homebrew/legacy-homebrew#24107, which has been completely merged and closed 5 days ago. I'll test it!

[christianbundy]

The bundle command is definitely very new, but it should be pretty stable. Let me know if you see any unexpected behavior – it's my biggest contribution to Homebrew so I want to make sure there aren't any surprises. Thanks!

[cloud8421]

Thanks @christianbundy! I wouldn't expect any and in the end it would be just an update with a few installs, no taps, dupes or casks. I have it on my local machine and it seems fine. Can I just ask you if there's an associated release number for that feature? Something I could potentially use to perform a preliminary check?

[allolex]

This is really cool. Anything to tighten up the configuration/installation!

Edit: OMG. I didn't scroll up to the top. @cloud8421 has been busy. Let me do a test install and check it out!

[christianbundy]

Woah, sorry about that @cloud8421 – didn't see your comment. There isn't a release number for that, but you could make sure that it's supported by running:

cd $(brew --prefix)
count=$(git rev-list HEAD --count)
if [ $count -gt 25122 ]; then
    echo 'Brewfile supported'
fi
cd - 2>&1 >/dev/null

This just counts number of commits in the Homebrew repo, and if it's greater than 25122 then Brewfile must be supported

[cloud8421]

Thanks again @christianbundy, that would work!

[cloud8421]

Thanks @allolex! I think it should be ok in general, however I know you have an RVM preference so that could be a problem ;-)

[allolex]

I've been using chruby since August. ;)