Tim Pope

Make me a small example project using `.projections.json` and I'll try to figure out what's going wrong.

A lot of compiler plugins uses `%-G%.%#` to aggressively hide all unparsed output, even helpful output, by default. With the built-in `:make`, this isn't a big deal, because the full...

From the `:help`: > ``` > X11 ~ > > Uses g:dispatch_terminal_exec, "$TERMINAL -e", or "xterm -e". > ``` The default is already `xterm -e`. All you're doing by setting...

Go for it.

It's designed first and foremost for source code identifiers, I don't want to change everything under the sun that looks vaguely similar. But I think it would be reasonable for...

> This would be very useful in Golang, as it's often we want to search and replace auto-generated code (so, e.g. `struct_name.StructName` -> `new_struct_name.NewStructName`. You can already do this. `:S/struct_name/new_struct_name/g`....

Rbenv ships with it's own `realpath` we could use. I agree, the cache location is weird. I don't remember why I did it that way.

I'm not sure how ripper compares to exuberant-ctags but I do like the idea of a pure Ruby solution. I am a bit hesitant to force the automatic installation of...

In a fresh ruby install, how would it ever be installed?

This code is ancient, but I'd say it's a safe guess I was aiming to specifically not to regexp escapes, limiting the magic to our own `{}` expressions. I was...