You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The justification for vim/emacs dynamically loading the merlin plugin was so that merlin can evolve its commands and the plugins that call them at the same time, so that when you upgrade to a new merlin, your editor, on startup, loads the fresh new plugin.
Vim-reason used to do the same. I've since pulled out the plugin logic from vim and pasted it in the vim-reason plugin itself, because the dynamic loading thing wasn't working as reliably as we'd hoped. This means if merlin ever changes how its queries work when the editor plugin will need to be manually updated to match that new version. But that's a fine tradeoff since the Reason community isn't ready to arbitrarily upgrade merlin yet anyway. It also makes distributing precompiled merlin binaries easier, since the binaries obviously don't carry these plugins with them.
The text was updated successfully, but these errors were encountered:
If I'm not mistaken, the merlin editor logic is dynamically loaded from merlin https://github.com/ocaml/merlin/tree/master/emacs
The justification for vim/emacs dynamically loading the merlin plugin was so that merlin can evolve its commands and the plugins that call them at the same time, so that when you upgrade to a new merlin, your editor, on startup, loads the fresh new plugin.
Vim-reason used to do the same. I've since pulled out the plugin logic from vim and pasted it in the vim-reason plugin itself, because the dynamic loading thing wasn't working as reliably as we'd hoped. This means if merlin ever changes how its queries work when the editor plugin will need to be manually updated to match that new version. But that's a fine tradeoff since the Reason community isn't ready to arbitrarily upgrade merlin yet anyway. It also makes distributing precompiled merlin binaries easier, since the binaries obviously don't carry these plugins with them.
The text was updated successfully, but these errors were encountered: