I'm not sure if I'll stick with this or not, but its default mode of
operation seems to be about the right amount of in-your-face, at least
for the stuff I've tried it on today:  Write the buffer with a syntax
error, and you'll get strong visual indicators of the error along with
the specifics.

Useful for shortcircuiting that part of the cycle where you run the code
before realizing you're missing a paren or whatever.

23fca3ed51

Depends on Unicode::CharName, easily installable with cpanp.

Conflicts:
	.vimrc

p & pul for pull, because i'm always doing this
s for status because why type two chars?
go for checkout because i'm always typoing it as this and why not
l for log

For @earthtopus on Twitter. Just a thought experiment, really, not a very
serious undertaking.

I learned here how to trap the next input character, and about <C-R>, which
lets you pull the contents of a register into insert mode, or press = to
pull in an evaluated expression.

https://github.com/stilldavid/home/blob/master/.vimrc#L73

Bit cheesy - think it's overriding a default, and reasonable-enough,
assumption that they're Perl.

Cutting way down on installed plugins, while I'm at it.

- latest git commits
- write all

I still think I am probably missing something here.