Tim Pope

I wonder if this is due to a recent change in RVM. Anyone else experiencing success or failures? (I don't have an RVM install handy to check at the moment.)

That autoload is unfortunate, but I do want this for doc files, README files, [Python files](https://github.com/tpope/vim-fireplace/blob/master/python/nrepl_fireplace.py), everything really. If this really is a pain point, I'd accept a bit of...

Remove the `resolve()` calls you tried to sneak in while you're at it. Make your case for that separately.

Based on vim-ruby/vim-ruby#252, I assume your primary issue is that the existing static logic is failing for JRuby? Could we fix that?

I'm sure it's possible, but that's the extent of my Nvm knowledge.

No desire to implement it but one fix could be to cache the `getchar()` result inside `opfunc`, and clear that cache beforehand when the map is invoked. Then we can...

Is this specific to surround.vim or can it be reproduced with other plugins?

I'll also throw into the mix that a false negative breaking a plugin repeat is probably better than a false positive breaking *all* built-in repeats. The direction I am moving...

I've gone with @tomtomjhj's solution as I find it a bit easier to reason about than the autocommand.

Fucking hell, it also impacts `'readonly'`, and that's only a warning so `catch` doesn't help.