Tim Pope

Bundler.vim aggressively caches, so if it happens repeatedly, the ultimate culprit is likely another plugin. Bundler.vim puts all your gems into `'tags'` and `'path'`, so if another plugin is doing...

Okay, so the next step is to add plugins back and figure out which is the trigger.

Try `doautocmd User Bundler` and see how slow that is.

That's on `compiler/bundler.vim`, which if you look inside I think you'll agree is a nonsensical culprit. Check the results with it deleted.

Regardless of the mechanics at play, that file itself isn't to blame. The profiler will give more useful information.

Okay, that's quite a few clues. With the required Ruby _not_ installed, Can you try the two Ruby commands listed above and report both their times and output?

How long does a single `system('echo')` take? Seems like speeding up your shell might be the low hanging fruit?

We already check `$GEM_PATH`; not sure what you hope to accomplish with `$GEM_HOME`.

Yeah no doubt that even in the best case `system()` is going to be slow. I was guessing yours was _very_ slow but mine is 20ms so maybe not. See...

With `RUBY VERSION` in the lock file now, maybe we could lean on that? What does it look like for JRuby?