Work around weird --remote skip of finally

Closes #152.
Fix deprecation error.

Without fix, this error message appears:

    bin/vim-ruby-install.rb:15:in `<main>': Use RbConfig instead of obsolete and deprecated Config.

    uninitialized constant Env::CONFIG
    Try 'ruby bin/vim-ruby-install.rb --help' for detailed usage.
Reformat installer.

Replace tabs with spaces. Ensure comments are properly lined up with code.
Basic "<<"-style heredoc indenting

If the closing delimiter is at column 0, keep it that way.
Merge pull request #153 from Ichimonji10/master

fix and reformat installer
Fix keyword symbols after parentheses

In response to the comment in #144.
Remove s:save_cpo when we're done with it
Simplify ruby*Constant syntax group matching
Highlight unicode characters in constants

Except those which are the first letter (e.g. `Ír`), as Ruby does not
recognize them as valid constants. (See also #138)
Fix constant definitions after comments.

These multi-line edge cases are almost impossible to find in the wild so I won't bother
supporting most of them for now.

Closes #164.
Merge branch 'unicode-constants' of https://github.com/amarshall/vim-ruby into amarshall-unicode-constants

Conflicts:
	syntax/ruby.vim
allow Gemfile gems to be parsed and required
Missing escape() for '*'

It's escaped the first time it's used, but not the second time, causing
a regex error for the string '**'.
Another missing "*" escape
Workaround for Vim 7.4's HTML indent
Merge pull request #167 from tek/master

allow Gemfile gems to be parsed and required
Add InterpolationDelimiter to the list of "string or delimiter"

Unsure if this won't break anything else :/.
WIP Retrying s:Match function

The s:Match function tries to find a pattern, but if the found one is in
a string or comment, it fails. However, it's possible that beyond the
string, there's a comma or something else that *also* fits the pattern
and will not be found.

There seems to have been an attempt to fix this issue by matching in
reverse with the unused `s:MatchLast` function, but it's not really used
anywhere, so it was removed.

The current implementation tries to match the same pattern on the rest
of the string after failing once.

Tests and documentation are needed. There may also be issues with
multibyte, not sure.
Don't match "line", match "lnum"

How did this ever work?
Tests for string interpolation problem