Vim interfering with Phoenix recompile after saving

Deactivate compile on save or any plugin that does it to lint. Or if you are able to, change them to use different folders than the project folder to temporary save, compile and lint.

You could tell vim to use an :editor MIX_ENV which is equal to :dev but does end up in ./_build/editor/ instead.

Those are the workarounds that I’m aware of. You can use those workarounds for any editor-plugin that compiles on save.

Thanks, not sure how to do that for Ale. I did confirm it is Ale doing it. I just removed it and the issue cleared itself up. Once I find the settings or another solution I’ll post it here.

Thanks for pointing me in the right direction.

When you start vim as in MIX_ENV=edit vim your-project, does it work?

Is credo linting working for you with Ale? for the last week it has stopped working, and it doesn’t show any credo issues anymore, and I was wondering if the same was happening to you…

Nope credo isn’t working either. I think it’s related. Because Phoenix doesn’t seem to think the file has changed when I save from Vim. I can live with out credo but restarting phx.server every few minutes is super annoying.

@NobbZ yes it does. Why would setting MIX_ENV=edit fix the issue?

Because you then use a different MIX_ENV, which compiles to ,/_build/edit instead of ./_build/dev, therefore Phoenix.CodeReload can actually compile stuff and realize it changed for dev as well.

Makes sense. I know I can’t set that in my .zshrc since mix phx.server would pick it up and cause the same issue right? This depends on mix phx.server starting in MIX_ENV=dev and the editor starting it in MIX_ENV=edit right?

Yes, it depends on the editor and phoenix are running in different environments.

Perhaps an alias vim="MIX_ENV=edit vim" would suffice?

Exactly what I was thinking. You sir are a champion. Thanks for the assistance.

But be warned, this will probably brake when you start a terminal in vim and run phoenix in that