Tim Pope

The only additional advice I can offer is try commenting out part/all of the syntax highlighting support in rails.vim and see if you can get the problem to go away....

I aim to port over the slightly different expansions from [projectile.vim](/tpope/vim-projectile) in the near future. This should enable solving half the problem with `{dirname}/_{basename}`. Speak up in tpope/vim-projectile#3 if you...

The basic logic for figuring out the diff line can [be found in `s:StageInfo()`](https://github.com/tpope/vim-fugitive/blob/bb466308282c3d3ef9007ecceb45db931f606ae7/autoload/fugitive.vim#L2026-L2040). I'd recommend duplicating it as a starting point. (Don't try to DRY it up.) If a...

Note the linked Fugitive PR is a prerequisite and the current bottleneck.

The way `rails credentials:edit` works is it decrypts `credentials.yml.enc` to a temp file, opens that temp file in your editor, and re-encrypts upon exiting the editor. Two rails.vim solutions spring...

Changing all the projections to use custom quotes sounds pretty invasive. I wanna know how this is handled in generators before I commit to that.

I don't know what this could be. You could try commenting out portions of `rails#buffer_setup()` and see if you can narrow down the cause.

It's a start, but narrower would be more actionable. You may need to dive into the `s:BufProjectionCommands()` definition or even deeper.

That maps to `s:app_commands()`, which in turn calls `s:app_projections()`. Nothing jumps out as suspicious in either of those so I guess you have more bisecting to do.

Does this happen with any `system()` call? If you add `call system('true')`, to your vimrc, does that also cause the problem?